We have successfully made platform enhancements on Saturday, September 11, 2021, from 1:00 p.m. to 5:00 p.m. PDT.
This maintenance window will deliver a new set of application lifecycle management (ALM) application programming interfaces (APIs) that provide more automation for managing the lifecycle of your applications. These ALM APIs also help workspace admins build more robust change management reports to easily meet regulatory and compliance requirements.
New ALM APIs allow Workspace Admins to:
Retrieve the full comparison report between two revisions
Retrieve the models that a revision has been applied to
Retrieve all of the revisions in a particular model.
When a model is in deployed mode, and you publish a production list to a dashboard, users are unable to insert new child items under the top level item.
In very rare circumstances, an API request can slow down a model or render it unavailable.
In rare cases, when you perform a syncronization, and the core on which the target model is stored is restarted, the model becomes inaccessible.
When a synchronization is unsuccessful, the target model does not rollback to its previous state. This can leave the target model incompatible with the source model.
In rare cases, transient network issues in Anaplan's infrastructure can result in API calls that execute processes to fail
When you refresh a connection in the Excel Add-in, the model returns an incorrect count for items in line item subsets.
When you try to run a model-to-model import using a process in CloudWorks, and the process creates the target model from the source model and runs an ALM synchronization between the models, the process is unsuccessful.
00360877 00364631 00366800 00367866
When you set up an import for a development model where the source and target are in the same model, then synchronize the development model to the production model, and run the import for the production model using CloudWorks, CloudWorks displays the import as successful. However, the history in the production model shows the import used the development model as the source when it ran.
When you import to a large list, the import is slow, even when there is nothing to import from the source.