Watch this Ask the Expert session to learn new ways to assign workflows in order to manage and govern decision assets.
Watch the Webinar
You will learn how to:
- Define custom workflows for your decision journey.
- Manage tasks within these workflows.
- Accelerate decision deployment with a governed approach.
The questions from the Q&A segment held at the end of the webinar are listed below and the slides from the webinar are attached.
Q&A
Can you only have 3 environments? We have more.
3 here was purely for demonstration purposes. I have worked with customers with up to 7 environments. There is no problem. You can have as many environments as you require, ArgoCD and Intelligent Decisioning and the workflow will work with as many as you have.
Does it only work with ArgoCD?
No. Argo CD was only an example. Other tools include Flux CD. There are a lot of CI/CD tools out there. The workflow allows you to call REST industry standard interfaces. It will work with most, if not all, of those CI/CD tools. It is very flexible.
What is a rolling update? Why would you not do one?
I mentioned that a rolling update is particularly useful. It allows you to replace containers without an outage. In the demonstration you saw that I had three copies of version 2.4 running. With a rolling update I could replace them with three copies of 2.5, one container at a time. So, there is never a situation where there is no service running. From a governance point of view, there is a small window, 2-3 minutes, where you will not be sure whether your users are going to get served by a 2.4 or 2.5 version of the decision. If that does not bother you or does not cause you any problems, then the advantage of having zero outage is useful. But if that is a concern and you want immediately to switch over to 2.5, then rolling update is not for you. You will need to use the replace strategy. You will have an outage while the last old container is stopped and the first of the new containers are started. SAS Intelligent decisioning can work with both.
Can I setup a time after which decisions are retired as part of the workflow?
I did not cover this. I want to show this in the initial step where you define your workflow. You can put certain time limits on the steps in the workflow or on the tasks that need to be completed, like a deadline. You also saw when you published a decision that you can set up a time to delay the publishing. So, I think you can set that up as well for the retirement staff. It is just a different type of step that you have within the workflow.
Recommended Resources
SAS Intelligent Decisioning Homepage
SAS Communities Decisioning Page - Blogs, What's New, Product Suggestions
Ask the Expert - SAS Intelligent Decisioning and SAS Model Manager Better Together
Ask the Expert - Segmentation Trees in ID
Please see additional resources in the attached slide deck.
Want more tips? Be sure to subscribe to the Ask the Expert board to receive follow up Q&A, slides and recordings from other SAS Ask the Expert webinars.
