
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-11-2024 12:56 AM - edited ‎09-11-2024 01:52 AM
Anyone else failing to use Service Builder when installing: Service Builder 3.1.3 and DPM 6.0.8.
When opening a service which is operational and attempting to submit we get the error from a validation script: Status can only move forward to retiring or retired or obsolete from operational.
I suspect this is only a symptom of another issue since we also see the following in the application log when opening a service in SB:
[ASB] Error while setting draft prefix for record name: [Draft] <ServiceName>
There is a new feature in that version which renames the draft with a prefix, and for some reason that fails in our environments.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2024 11:29 PM
Resolved by support and development team supplying three update set patches as a workaround until a permanent fix is in the product.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-25-2024 10:49 PM
The development team is working on a fix, ask your support rep to look into PRB1804842 and see if it fits your symptoms.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2024 11:29 PM
Resolved by support and development team supplying three update set patches as a workaround until a permanent fix is in the product.