New features and enhancements
New translatable property in the Language IDs IDO
We added a new derived property to the Language IDs IDO that allows developers to implement a field that displays a translatable description of the Language Code. For example, instead of Spanish (Spain), you might want to display the description as Español (España). This new feature requires that translatable strings be used. For more information, see the topic "Providing for localization in language fields" in the online help.
Modifications to replication document metadata processing
We made several modifications to the way Mongoose handles replication document metadata, including these:
- We now enforce read-only handling of selected replication document metadata, depending on Access As credentials.
- Extensibility of replication document metadata is now accomplished by allowing elements and attributes to be copied with the user’s Access As identifier applied. The copied metadata can then be modified as required.
- Developers can use the App Metadata Transport tool to export custom elements and attributes of replication document metadata.
For more information, see the online help.
Ability to retrieve BOD element position
On the Replication Documents Elements form, you can now append the GETPOSITION function to the value of the BOD Tag Name field to retrieve the position of the element during inbound BOD processing.
This feature only works for inbound processing with value type of value.
FormSync enhancements
We reduced the sequence-related prompts by suppressing all container sequence and tab order prompts. The sequence-related prompts no longer appear during the completion of the Automated Upgrade or Interactive FormSync. All sequence-related conflicts are resolved in favor of the customer's sequence at the end of the FormSync synchronization.
We streamlined the processing of event handlers when using FormSync. This primarily provides for improved default behaviors of event handlers when no KEEP keywords are provided. These changes in behavior apply only if none of the original vendor handlers (SOURCE VENDOR) are modified by site, group, or user versions, and KEEP keywords are not used on any of the event handlers. For detailed information, see the topic "KEEP processing during form synchronization" in the online help.
New mechanism to prevent users from altering core SQL tables
System administrators can now use the Metadata Access Controls form to restrict access to application metadata and prevent users from altering core SQL tables. Currently, you can use this form to restrict access only to SQL tables. This new mechanism enables you to set the access type of SQL tables to , , or . The restrictions apply when you modify SQL tables in the SQL Tables form, the SQL Columns form, and the UET Table/Class Relationships form.
The Metadata Access Controls form is accessible only to authorized system administrators and is read-only in multi-tenant cloud environments.
Improved the validation procedure and restrictions of the Application Schema Table Metadata form and Application Schema Column Metadata form
We added validation procedures and restrictions in the Application Schema Table Metadata and Application Schema Column Metadata forms. In the Application Schema Tables Metadata form, the Table Name field checks whether the table name exists as a valid table from SqlTables. The SiteColumnName field checks to see if the site column name is an existing column of the selected table. Also, the View Name field validates whether the input name exists as a Table Name or as a View Name from the current collection.
For both forms, if or the Enforce Prefix From Access As is set to 1 in the Process Defaults form, updating the records with table names that do not start with the current AccessAs value is restricted.