Target systems with Draft mode
Niek de Melker
When editing a target system, the changes are immediately in production. It would be nice if the auto safe sets the changes made in a draft state so we can prepare changes in a target system and publish it when everything is tested and ready to be production. Just like the business rules.
why i want this: Sometimes we need to troubleshoot a target system, and this may require some changes in the scripts, now we must be very careful to not safe some tests. this can result in excessive logging by mistake of even wrong results to a target system.
other times I need to prepare changes that have to be reviewed before going to production, a draft in HelloID would be the perfect place to have this.
This also applies for the source systems
K
Kim B.
If this requenst can be granted, is there also the option to high light or a note what's in draft? I find the problem with drafts (in business rules) that if my colleague makes a draft, I can't see what the change is. Now sometimes I have to push publish and hope for the best. And unfortunately there is also no option "Go back to previous version", only a reverse option when a change is still in draft. Once you publish you can never go back.
R
Rick van den Dijssel
Hey Niek de Melker, thanks for your feedback! I have a few more questions for you:
- Can you provide more details on the review process you currently have in place for changes before they go to production?
- What specific features would you like to see in the draft mode for target systems?
- How often do you find yourself needing to make changes to the scripts for troubleshooting purposes?
Niek de Melker
Rick van den Dijssel Hi Rick,
- the review process depends on the change and customer. this can be a simple second check by a colleague or a validation of dryrun results by the customer.
- the same as with business rules. After making changes i want a simple button to revert or publish the changes, this way we can have auto-safe and don't have to back-up scripts before making a change.
- as we manage over 30 tenants, this starts to get quite a lot. older target systems will eventually start failing as API endpoints change or get deprecated, or the powershell engine changes. sometimes there is a misconfiguration only affecting a single user. I guess we have on average 2-3 tickets a week requiring small changes, and 1-2 every month requiring bigger changes.