The Content Sandbox is where you can draft and publish your articles for review by a Content Manager or Administrator. Click Create an article to begin the process. Refer to the toolkit for article creation tutorials, best practices, style guides, and templates.

Once your article is ready for review, click the Save & Request Publication button to alert Content Managers and Admins.

Note: This is a shared space for all content contributors. Please respect the work of others. Do not edit or attempt to edit content that is not your own. Doing so will result in administrative actions that may include revocation of content contributor privileges, removal of contributed content, and even account banning.

Please contact community@anaplan.com with any questions.

Sort by:
  Introduction The new Anaplan APIs and integration connectors leverage Certificate Authority (CA) -issued certificates.   These certificates can be obtained through your company's intermediary CA (typically issued by IT) or by purchasing it from a trusted Certificate Authority.  Anaplan clients leveraging REST API v2.0 use both basic authentication and CA certificate based authentication.  Examples of these clients include Anaplan Connect 1.4, Informatica Anaplan Connector, and Mulesoft 2.0.1. If you are migrating your Anaplan Connector scripts from v1.3 to v1.4, your available options for authentication will be basic authentication or CA certificate based authentication. This article outlines steps to perform in preparation for CA certificate authentication. Steps to prepare for CA certificate authentication Obtain a certificate from a CA authority Convert CA certificate to either a p12 or pfx file Import CA certificate into Internet Explorer/Mozilla Firefox to convert to a p12/pfx file Export CA certtificate from Internt Explorer/Mozilla Firefox to covert to a p12/pfx file Optional:  Install Openssl tool Convert the p12/pfx file into a Java Keystore Manage CA certificates in Anaplan Tenant Administrator Validate CA certificate authentication via Anaplan Connect 1.4 script. Obtain a certificate from a CA authority You can obtain a certificate from CA authority by submitting a request or submit a request with a certificate signing requiest (CSR) containing your private key.  Contact your IT or Security Operations organization to determine if your company already has an existing relationship with a CA or intermediary CA. If your organization has an existing relationship with a CA or Intermediate CA you can request a client certificate be issued for your integration user. If your organization does not have an existing CA relationship, you should contact a valid CA to procure a client certificate. Convert CA certificate to either a p12 or pfx file Import CA certificate into IE/Firefox to convert to a p12/pfx file This section presents steps to import CA certificate into Internet Explorer and Mozilla Firefox.  CA certificate will be exported in the next section to either a p12 or pfx format. CA certificates may have .crt or .cer as file extensions. Internet Explorer Within Internet explorer, click on the Settings icon and select Internet option    Navigate to the Content tab and then click on Certificates.     Click Import to launch the Certificate Import Wizard.    Click Browse to search & select the CA Certificate file.  This file may have a file extension of .crt or .cer.     If a password was used when requesting the Certificate, enter it in this screen. Ensure that the “Mark this key as exportable” option is selected and click Next    Select the certificate store in which to import the certificate and click Next     Review the setting and click Finish     The certificate should appear in the certificate store selected.   Mozilla Firefox Within Firefox, select Options from the settings menu    In the Options window, click Privacy & Security from the navigation pane on the left. Scroll to the very bottom and click on the View Certificates… button    In the Certificate Manager, click the Import… button and select the certificate to convert and click Open   If a password was provided when the certificate was requested, enter that password and click OK    The certificate should now show up in the Certificate Manager   Export CA certificate from IE/Firefox to convert to a p12/pfx file This section presents steps to export CA certificate from Internet Explorer (pfx) and Mozilla Firefox (p12). Internet Explorer (pfx) Select the certificate imported above and click the Export… button to initiate the Certificate Export Wizard      Select the option “Yes, export the private key” and click Next   Select the option for Personal Informatica Exchange – PCKS #12 (.PFX) and click Next    Create a password, enter it and confirm it in the following screen.  This password will be used later on in the process.  Click Next to continue    Select a location to export the file and click Save    Verify the file location and click Next      Review the export settings, ensure that the Export Keys settings says “Yes”, if not start the export over.  If all looks good, click Next. A message will appear when the export is successful.      Mozilla Firefox (p12) To export the certificate from Firefox, click the Backup… button in the Certificate Manager.  Select a location and a name for the file.  Ensure that the Save as type: is “PKCS12 Files (*.p12)”. Click the Save button to continue    Enter a password to be used later when exporting the public and private keys. Click the OK button to finish   Install openssl tool (Optional) If you haven't done so already, install openssl tool for your operating system.  List of third party binary distributions may be found on www.openssl.org or here.  Examples in this article are shown for Windows platform. Convert the p12/pfx file into a Java Keystore Execute the following toto export the public and private keys exported above.  In the commands listed below, the values that are customer specific are in Bold Italics.  There is a screen shot at the end of this section that shows all of the commands run in sequence and it shows how the passwords relate between the steps. Examples in this article assume location of the certificate as the working directory.  If you are executing these commands from a different directory (ex: ...\openssl\bin), then ensure you provide absolute directory path to all the files. Export the public key Public key will be exported from the certificate (p12/pfx) using openssl tool.  Result is a .pem (public_key.pem) file that will be imported into Anaplan using Anaplan's Tenant Administrator client.   NOTE:  The command below will prompt for a password.  This password was created in steps above during export. openssl pkcs12 -clcerts -nokeys -in ScottSmithExportedCert.pfx -out public_key.pem Edit the public_key.pem file Remove everything before ---Begin Certificate --- (section highlighted in yellow).  Ensure that the emailAddress value is populated with the user that will run the integrations. Export the Private Key This command will prompt for a password.  This password is the password created in the export above.  It will the prompt for a new password for the Private Key. It will also ask to confirm that password.  openssl pkcs12 -nocerts -in ScottSmithExportedCert.pfx -out private_key.pem Create P12 Bundle This command will prompt for the private key password from the step above.  It will the prompt for a new password for the Bundle. It will also ask to confirm that password. openssl pkcs12 -export -in public_key.pem -inkey private_key.pem -out bundle.p12 -name Scott -CAfile public_key.pem -caname Scott In the command above,  public_key.pem is the file that was created in the step "Export the Public Key".  This is the file that will be registered with Anaplan using Anaplan Tenant Administrator.  private_key.pem is the file that was created in the step "Export the Private Key". bundle.p12  is the output file from this command, which will be used in the next step to create Java Keystore. Scott is the keystore alias. Add to Java Keystore (jks) Using keytool (typically found in <Java8>/bin), create a .jks file.  This file will be referenced in Anaplan Connect 1.4 scripts for authentication. Command below will prompt for a new password for the entry into the keystore. It will also ask to confirm that password.  It will, then, prompt for the Bundle password from the step above. keytool -importkeystore -destkeystore my_keystore.jks -srckeystore bundle.p12 -srcstoretype PKCS12 In the command above: my_keystore.jks is the keystore file that will be referenced in your Anaplan Connect 1.4 scripts. bundle.p12 is the P12 bundle that was created in the last step   Manage CA certificates in Anaplan Tenant Administrator In this step, you will add public_key.pem file to list of certificates in Anaplan Tenant Administrator.  This file was created & edited in the first two steps of the last section. Log on to Anaplan Tenant Administrator.  Navigate to Administration --> Security --> Certificates --> Add Certificate.   Validate CA certificate authentication via Anaplan Connect 1.4 script. Since you will be migrating to CA Certificate based authentication, you will need to upgrade your Anaplan Connect and associated scripts from v1.3 to v1.4.  Community article, Migrating from Anaplan Connect 1.3.x.x to Anaplan Connect 1.4 will guide you through necessary steps.  Follow the steps outlined in the article to edit & execute your Anaplan Connect 1.4 script.  Examples provided (Windows & Linux) at the end of the article will validate authentication to Anaplan using CA Certificates and will return list of user's workspaces in a tenant.  
View full article
Anaplan addresses the current ways of governing budgets & spend that create challenges in sustaining savings from Zero Based Budgeting (ZBB) Workforce planning initiatives
View full article
This article will guide you through the process of creating custom views to see a list of records that meet your filter criteria. If at any point you would like assistance, please  create a support case in your Case Portal, or  contact Customer Support  via email, phone, or chat.  Under List View Controls, select New. Or, click Clone to make a copy of the current list view. Give your list a name. Choose who can see this list view: just you, or all users, including Partner and Customer Portal users. Click  Save . The Filters panel appears. Click Show me, then select All objects or My Objects. Click Done. Add and set filters to view only the records that meet your criteria. You have different options depending on the field you want to filter and the operator you choose. Filters only support values between the minimum and maximum for a signed 23-bit integer, or between 1 and 2,147,483,648. A value outside of this range disables that filter. Click Add Filter. Select the field to filter, an operator, and a value. Depending on the type of field you selected, you can either select a value or enter one of your own. Click Done. Note: Entering illogical filter criteria, such as someDate <= null , can cause unexpected behavior in a list view. When you use a list view in a more strict context, such as with a Visualforce standard list controller, illogical filter criteria can cause errors To add logic that further refines which records appear in your list view, click Filter Logic. To reference filters in your logic statement, use the number assigned to each filter. Important: Include every filter number in your logic statement. You can’t have filters that aren’t referenced in the logic statement. Click  Save . The view appears in the list view drop-down list so you can access it later. Optionally, choose and order the columns in your list view. From the List View Controls menu, Select Fields to Display. Use the arrows to add, remove, and reorder your visible fields. Click Save. Additionally, actions you can take for list views are available in the List View Controls menu.  Note: In list views, you see only the data that you have access to. You see records that you own or have read or write access to, and records shared with you. List views also include records owned by or shared with users in roles below you in the role hierarchy. You can see only the fields that are visible according to your page layout and field-level security settings. Operand  Definition AND Finds records that match both values. 1 AND 2 OR Finds records that match either value. 1 OR  2 NOT Finds records that exclude values. For example, Filter 1 is Industry equals Biotechnology. You set filter logic as NOT 1. Your report returns records that don’t have Biotechnology as the Industry value.
View full article