From Admin console, select Object Type Definitions | Change Documents. Click NEW and select "Change Document Type". Add the new change document type. Click on OPTIONS tab, enable necessary selections and click "OK".
issue can be reproduced as follow : a_ run crdb command to create a new database from cm_typical demo database b_ define a Jira external request provider in admin console then the message "No attributes defined for this request provider" is displayed
If a template user has direct individual user assignments rather than group privileges then this can potentially mean that a very large number of records needs to be created per user. For example, if the template user has individual field privilege records for every field defined in all applications, then each of these field privileges is a row in TS_FIELDPRIVILEGES table.
Edit the new DDF file from within the Contribution Setup screen. You should see the same fields defined in the new DDF file as were in the original DDF file. Verify that the settings were copied correctly, and make changes as needed.
Where more than one value exists a second (or more) row is created but only including the additional required data, not all the others. Therefore what you are seeing is correct and if you viewed the additional columns in the view you would see the extra data. With no multi-value attributes defined , no more of these rows will be created.
When defining this path, you must use forward slashes (/), even for Windows paths. 4 If you will define a desired attributes XML file, which allows you to customize precisely which content fields in a contribution document are copied to the database during deployment, add the following line to specify the path to the desired attributes XML file: desiredAttributeFileName=full path to the desired attributes file
A: If a field has been defined in a previous copy of the XML but no longer exists in the current XML, the field is marked as deleted in the database and removed from the TS_FIELDORDERINGS table. The same is true for any selections that are no longer found in the XML.
The body section of the Database Query component formats the display of the query results. The component can define unique formatting for each row and field in the result set, or repeat the same formatting for a series of rows or fields .
