- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm migrating Enterprise Guide custom task to SAS Studio and find that the best solutiong is to create a custom step with the same UI.
Using SAS Studio custom task is not an option because it can not be added to a SAS Studio flow.
Here are my challenges,
- when a column in a column selector control is selected, user can set some additional properties that is needed when generating sas code.
- the step has two input data and user can set the join conditions
- columns of the output data can be inherited from either of the input data or be calculated using input data
These functions are implemented on EG custom task by using c#.
On SAS Studio these can be done by combining some built-in steps with simple custom steps, but is it possible that I can create my own controls so I can implement all these functions in one step, so that user can do all these in a single custom step?
I am using Viya 2022.1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Custom steps can be added to a flow:
How to make a custom step:
From the documentation:
Note: The Custom Step functionality is available only if your site licenses SAS Studio Analyst or SAS Studio Engineer. Custom steps are not available in the Interactive perspective.
What Version of SAS Studio Are You Running?
https://documentation.sas.com/doc/en/webeditorcdc/v_024/webeditorag/p14ailcd9ouczan1pph34bgl84b6.htm
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I'm running SAS Studio Engineer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
See https://www.youtube.com/watch?v=vkI0mysfAkQ
for an example how to create a custom step and add it to a flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Thanks @DJongman .
I do know how to create custom steps and add them to flow.
I'm asking for solutions for the points that I listed in my first post that can not implement (or I don't know how) on the current version of SAS Studio