| |
Results |
|
Notification on Aux Table won't send email if permissions are inherited from group or role.
|
This only pertains to email notifications on Aux Tables not Primary Items.
|
|
|
|
Associated roles not enabling users for User field in auxiliary tables
|
Create a "user" field in an aux table and, in the properties in Mashup Composer associate the field with some roles . Go to Mashup Administrator and you will see that the roles are listed as "Acting as" selections, with a status of "Automatic", but 2-clicking makes no difference and no users ever get listed as available choices in Mashup Administrator, nor in the UI.
|
|
|
|
KM-Dim7: How to recalculate pending lists and reset the role table?
|
KM-Dim7: How to recalculate pending lists and reset the role table ?
|
|
|
|
User fields in Auxiliary tables do not honour role privileges
|
Using only roles to assign users to user fields in an auxiliary table causes these user fields to appear, when a new item is created in that auxiliary table. Users that are part of the assigned roles appear to be invalid for the field. This is the same whether the item is created by hand in the web interface or whether webservices are used.
|
|
|
|
Global Process App Roles
|
As of SBM 10.1.5, You can now add roles to the Global Process App, which enables you to manage role privileges for auxiliary tables exclusively in the Global Process App. The privileges are granted to users and groups that you assign to the roles on the base project in Application Administrator.
|
|
|
|
Release Control 6.0: RLC Deployment Log table is missing
|
After installing RLC 6.0, you need to give the correct roles to each user/group. During this step, you must also give permissions to the "RLC Deployment Log" AUX table. This document explains what to do if that AUX table is missing.
|
|
|
|
Invalid Role reference in Role Assignments causes snapshot to fail
|
If an attempt to take a snapshot fails, but Mashup Manager is able to "get" the Mashup from the Application Engine, one of the possible causes could be invalid Role references in the Role Assignments table (TS_SECURITYCONTROLS). There could be records pointning to non-existent Roles.
|
|
|
|
Mashups may fail to deploy if they contain auxiliary tables that were deleted
|
Mashups fail to deploy if they contained auxiliary tables that were deleted, and role privileges were set for the deleted tables . The error says: "Failed to find Table context for PrivilegeKeySet."
|
|
|
|
Adding selection values to User, Multi-User, Multi-Group fields in auxiliary tables
|
You can add selection values to auxiliary table User, Multi-User and Multi-Group fields by using role association to fields in Composer. To do this select the relevant User, Multi-User or Multi-Group field, switch to the Options tab and then select a number of Associated Roles . Finally associate these roles with users or groups in SBM Application Administrator.
|
|
|
|
sbmadminservices72 SetGroupRoles Error picking wrong RoleID for two same named Role names
|
As an example, we get 2 projects from 2 separate tables . The problem here is that the system caches the role list that is returned, assuming that the entire request is for a single table. If all projects listed are from the same table, there is no defect.
|
|
|
