{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":2292,"path":"application-development/r_CreationRestrsAcrossAppScopes.md","title":"Creation restrictions across application scopes","bundle":null,"doc_type":null,"release":"australia","body":"\n# Creation restrictions across application scopes\n\nThe system restricts the creation of some configuration records when the current application scope does not match the application scope of the configuration record's target table.\n\nConfiguration record creation restrictions prevent one application from making unwanted changes to another application's data tables. These restrictions only apply when you create a configuration record whose target table belongs to another application. Configuration records that belong to the same application scope do not have these restrictions.\n\nThe system always enforces the following creation restrictions when a developer adds a configuration record belonging to another application scope.\n\n\n
\n\nConfiguration record type\n\n\n\nCreation restrictions when target table is in another application scope\n\n
\n\nAccess controls\n\n\n\n- You can only create field-level access controls with a role-based requirement.\n- You cannot create table-level access controls for a table in another application scope.\n- You cannot create field-level access controls that apply to all fields.\n- You cannot create access controls that use conditions.\n- You cannot create access controls that use a script-based condition.\n\n
\n\nBusiness rules\n\n\n\n- You can create a rule where **When** is async with any of the following options:\n - Insert, Update, and Delete database operations. You cannot select Query.\n - **Set field values** actions and scripts \\(the **Script** field\\).\n- You can create a rule where **When** is before with any of the following options:\n - Insert, Update, and Delete database operations. You cannot select Query.\n - **Set field values** actions only. You cannot write scripts and you cannot abort the database transaction.\n\n
\n\nCalculated fields\n\n\n\nYou cannot create calculated fields for tables in another application scope.\n\n
\n\nData policies\n\n\n\n- You cannot create data policy rules for fields in another application scope.\n- You cannot make a field mandatory.\n\n
\n\nField styles\n\n\n\nYou cannot create field styles for fields in another application scope.\n\n
\n\nForm sections\n\n\n\n- You cannot modify existing form sections created in another application scope.\n- You can create new form sections.\n\n
\n\nRecord producers\n\n\n\nYou must have create access to the application table to create records from a record producer.\n\n
\n\nUI policies\n\n\n\n- You cannot create UI policy rules for fields in another application scope.\n- You cannot make a field mandatory.\n\n
\n\nUI script\n\n\n\nYou cannot create a global UI script from a scoped application.\n\n
\n\nViews\n\n\n\n- You can create new views.\n- You cannot modify existing views created in another application scope.\n\n
"}}