Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Current user option not available for Rule Condition Added for MultiUserField
The ability to check for " Current User " was omitted when this facility was first made available. It will be added in a later release.
CMS-XML Error "Incorrect current password" when adding users to the E-mail Notification CC Users
On the User Profile, on the General tab, when you start typing in the "E-mail Notification CC Users" field, a new field called "Current Password" is added to the screen. Then, when you click Save Profile, you get error "Incorrect current password".
CMS-XML DIM10: Users with Add/Edit Detailed Description Privilege cannot edit the detailed description of existing Requests
In addition, the user cannot edit the detailed description of existing Requests. Customer has verified that the Add /Edit Detailed Description privilege is enable under Request privilge for General Grant Rule "Object is in the user's inbox or user has current role."
CMS-XML Dim7: To maintain the "old style" user ID convention use the CUSR command. This a command line only operation in v7.1 or newer. UREG is now the default for adding new users to Dimensions via Process Modeller and can be used via the command line too.
If the choice is to use the "new" convention then UREG can be used from the command or you can simply add user via process modeller. UREG is now the default for adding new users to a base database.
CMS-XML Form Action to check (Current User) is in Multi User Field does not work if only the Group is in list
- add a Multi User/Group Field (GROUPSANDUSERS1) to your process app (option Groups & Users) - add the field to a custom form - add a transition form action to this form with the following logic
CMS-XML Users are required to provide their current password when they attempt to change their password or e-mail address in their user profile.
To change this default behavior: 1. Allocate a new TS_ID for the new Setting record to be added by updating the TS_LASTIDS table. UPDATE TS_LASTIDS SET TS_LASTID = TS_LASTID + 1 WHERE TS_TABLEID = 56;
CMS-XML DIM10: When a user changes the current project in the Web Client with the function "Set current project" (SCWS), the system doesn't change the current product.
When a user changes the current project in the Web Client with the function "Set current project" (SCWS), the system doesn't change the current product. If the user doesn't notice that fact and adds items, the items are created in the wrong product.
CMS-XML SDA: Agent: Agent does not appear: java.lang.SecurityException: The current user cannot create subresources.
9. Restarted Serena tomcat 7 service in SDA server 10. Corresponding entry is not added to Resources and Agents 11. Found the following error in SDA log
CMS-XML How to use readdb and makedb to add, change, or remove users, groups, and privileges
(To be able to run makedb, the keywords have to be in this order. This is the default for current ACDBs, but a file that was last updated by a very old Version Manager release may have a different order. If so, re-sort the sections so all PRIVILEGE entries come first, followed by all USER entries and finally the GROUP entries, if any.)
CMS-XML KM-Dim7: Cannot add items to workset as a normal user
2 = Any user with a role can update workset contents 3 = case 1 and case 2 If you do not enter a flag to set then the current setting will be displayed.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs