The attached PCLI script scans the workfile location(s) for the given project(s) and automatically checks in changes to existing files and adds files that don't currently exist in the project. The script does not
In a Mashup where certain fields are hidden from a users form (e.g by using a custom form or by the user not having the privileges to see them), if these fields are being changed prior to the user reaching that form (for example through a pre-transition Mashup Script ), these fields are being reset and submitted as containing (None).
Script changes which update the TS_USERSETTINGS table are successfully updated in the database and the table affected is not cached but the change is not immediate in the user workspace. The changes made do not take affect until the web server is restarted. Attempts to create records in the CacheActions table to force a read to the table does not work.
KM-Dim9: There is no way to change / modify revision number on an existing item revision. This value is present in multiple tables within the schema, and Support does not have a script to update this value, nor do we have a schema description that will allow
In the ZMF 5.5 to 5.6 Migration Guide, page 51 describes all the steps to create the IA table and the new BUN table. It even tells you to run the Full IA job after the ZMF V5.6 task comes up (point #4). However, in the 'Sample Conversion Day Script ' on pages 60 + 61 there is no mention of the IA and BUN table jobs or when to run the Full IA job to populate the tables.
BAE SYSTEM reproduced on dim8.0.5 dim9.1.3 and dim10.1.0.2 When you run the RI from the command line (pcclient console or ms-dos) and update an attribute for the new revision with the same value that it had before, you will get an operation complete, however the attribute won’t be updated in that new revision….. Steps to reproduce
