Toggle Sidebar
  • Recent updates
    • Post is under moderation
      I do agree!!! And an Error Messages manual is needed too.
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Francisco Jose Gallego
      Dimensions users has problems with the error messages. They say that are too complicated to undestand what happens. In most cases, they forget to relate a request in a deliver operation and they get t...his huge error message:  c:temptestDLLnewFile.rtf file received Error Using Stream 'HBRM_WEB:TEST_DLL'.Using 'D:Program FilesSerenacommontomcat8.0workCatalinalocalhostdimensionse4p8t873.dirDV' as the Stream work area.Scanning local work area: less than 1 microsecondSCWS "HBRM_WEB:TEST_DLL" /DIRECTORY="D:Program FilesSerenacommontomcat8.0workCatalinalocalhostdimensionse4p8t873.dirDV" /NODEFAULT /NOCHECKWarning: There were errors while uploading files from the specified network node. Please check the upload log.Updating files: 0.05 secCommitting structure changes: less than 1 microsecondCOR3200234E Error: Delivery aborted.Creating new item revision for 'D:Program FilesSerenacommontomcat8.0workCatalinalocalhostdimensionse4p8t873.dirDVDLLnewFile.rtf'COR0005162E Error: To create a new Item revision of type SRC you must specify a valid requestCOR0006384E Error: Failed to create Item for 'D:Program FilesSerenacommontomcat8.0workCatalinalocalhostdimensionse4p8t873.dirDVDLLnewFile.rtf' c:temptest Associated metadata transferred Removing temporary files Operation completed The important part of this message is only: "COR0005162E Error: To create a new Item revision of type SRC you must specify a valid request". The messages are impossible to customize, even using Event Callouts. It would be great to improve error messages, making them simpler. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Francisco Jose Gallego
      Relationship between item revisions and Requests is made wrongly when the Request differs My "complaint" is about Dimensions behaviour when relating ítem revisions with a Request. Scenario 1 For the... first revision 1 of an item, when it is created, I relate it with a Request RQ_ 1. The relationship is establisshed In Response To with this Request. Then, I create a new revision 2 for this item and I relate it with the same Request RQ_ 1. This way, the relationship between revision 1 and Request RQ_ 1 is changed to Affected and revision 2 is related In Response To with Request RQ_ 1. Dimensions works fine as both revisions has a relation with Request RQ_ 1, one in Affected and the other In Response To. Both revisions were created because Request RQ_ 1 was required, they (both) have to do with RQ_ 1. If you query, you select Request RQ_ 1, two revisions appear, both revisions are related. And it is OK because revisions 1 and 2 were required for Request RQ_ 1. The "effort" to solve Request RQ_ 1 cost two revisions (revisions 1 and 2). This scenario 1 is absolutely OK. Scenario 2 For the first revision 1 of an item, when it is created, I relate it with a Request RQ_ 1. The relationship is established In Response To with this Request. Then, I create a new revision 2 for this item and I relate it with a different Request RQ_ 2. This way, Dimensions relate revision 1 with Request RQ_ 2 as Affected and revision 2 is related In Response To with Request RQ_ 2. Of course, revision 1 is kept related In Response To with Request RQ_ 1. Dimensions should not have related revision 1 with Request RQ_ 2 because this revision has nothing to do with this Request. Revision 1 was created because Request RQ_ 1 required it but not Request RQ_ 2 which is required just for revision 2. If you query, you select Request RQ_ 2, two revisions appear, both revisions are related but, I repeat, revision 1 has nothing to do with this Request. It seems that revisions 1 and 2 were required for Request RQ_ 2 and it is not true!!!!! Only revision 2 should have been related to Request RQ_ 2. The "effort" to solve Request RQ_ 2 cost just one revision (revision 2) and not two revisions (revision 1 and 2). This scenario 2 is wrong (in my opinion), Dimensions does not do it as it should. Conclusion Dimensions should distinguish between what Request an item revision is related to: if when an item revision is created (revise item or checkout) it is going to be related with the SAME Request that the revision is based on, both relationship (Affected, In Response To) must be made but if it is a DIFFERENT Request, just one relationship should be made. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Francisco Jose Gallego
      Francisco Jose Gallego updated their profile picture
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      David Goodale
      David Goodale is now friends with Francisco Jose Gallego
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Paul  Caruana
      Paul Caruana is now friends with Francisco Jose Gallego
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Dave Meier
      Dave Meier is now friends with Francisco Jose Gallego
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Dimensions CM to show submission progress of deployment Currently, Dimensions CM takes a long time to process the submission of the deployment of baseline. The user is not aware the system is process...ing. The submission may take a few minutes to complete. More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      There must be a parameter /REQUEST in GREP comand If you use GREP command for searching and replacing and CM Rules are enabled, you get an error because a Request has not been informed.... It is true ...but there is no way to do so. The woraround is disabling CM rules while searching and replacing!!! More
      Stream item published successfully. Item will now be visible on your stream.
    • Post is under moderation
      Rose Wellman
      Rose Wellman is now friends with Francisco Jose Gallego
      Stream item published successfully. Item will now be visible on your stream.
  • No blogs available.

  • DateTitle
    17/05/2018 Relationship between item revisions and Requets
    22/12/2015 Relating a Request when searching and replacing with GREP command

Recent Tweets