Hi,
The current limit of 60 chracters restricts the users to make sophisticated codes in complex usecases. It would be great if this limit cna be extended.
Thanks.
Nice suggestion.. this leads to the list type as numbered even though not required.. I support this technical limitation should be extended to probably 100 chars..
255 bytes to be aligned with varchar formating specs would be right.
All End Users and Executives experience this issue. When the model locks up (from integrations, inputs, etc) in the UX, all users see is a "Model is busy" without any context. It would be great if: They can see who is making the update They can get an estimated time of the model being busy This is key - When they see…
【Current Behavior & Challenge】 In the Anaplan UX, the History feature does not currently respect the filter settings applied to a Grid Card.When a user maximizes a Grid Card or selects the entire grid to view History, the results include the audit trail for rows that are filtered out (hidden) on the screen. 【Business…
Currently, the official documentation for connecting CloudWorks to Amazon S3 provides a broad IAM policy example that includes s3:DeleteObject. Connect to Amazon S3 | Anapedia However, from a security governance and "Principle of Least Privilege" perspective, many organizations require more granular control over these…