Copy and paste attached prompt definitions into another SAS EG project

[Brian]

Hi all

I'm interested in copying and pasting a program (w/ Prompts defined and attached) from one SAS EG project into a new SAS EG project (w/ No Prompts Defined). While I'm able to copy and paste over the program, the attached prompts do not carry over despite a prompt icon showing for the program in the Project Tree.

I'd like to avoid using the GUI to redefine reusable prompts with each new SAS EG project. I understand there is no way to "pop" any kind of interactive window in SAS EG. (i.e. %window, %display)

https://communities.sas.com/message/27045

It would be nice if a future enhancement would allow SAS EG to dynamically define and call prompts (especially from an external SAS program).

I understand SAS EG automation model can supply values for project prompts. Anyone know if SAS EG automation can dynamically create project prompts?

http://support.sas.com/resources/papers/proceedings12/298-2012.pdf

Any thoughts?

Thanks for your help in advance!

[jakarman]

aside defining prompts within each EG project you could define the prompts within the SAS metadatabase.

Organizing prompts at that area is having those able to be shared. What is the issue with that one?

[ChrisHemedinger · Accepted solution]

Brian,

For automation-enabled prompts, you could use this task:

Process Interruptus: a custom task to pause your process flow - The SAS Dummy

These are outside of the built-in prompts that EG supports in the project.

EG does not support creating new prompts within automation, but you could have your automation script display a prompt (in VBS or PowerShell or whatever you're using) and then create/run a program in the CodeCollection object.

And copy/paste of items that carry the prompts with them -- that's on the list for the next version of EG (not 7.1, which is out now, but the one after that).

Chris

[Brian]

Thanks Chris for your help. I'm looking forward to seeing it in the next EG update.

In the interim, I'll review the feasibility re: the two options you've shared. I appreciate your work on developing these custom tasks. Any opportunity to integrate this add-in functionality back into a future SAS EG version would help improve implementation/adoption.

Brian

[jakarman]

Still the question what is not there with the metadata approach. This is the central point and strategic way sas institute is moving.

If you may believe all their work and presentations on their solutions strategy.   

[ChrisHemedinger]

Jaap,

Shared prompts can work only with SAS stored processes, not just any arbitrary SAS programs.  And not every installation is using metadata to its fullest; there is a wide spectrum of how different sites leverage metadata (or elect not to...).

Chris

[jakarman]

@Chris technically you are correct. The difference is hearing and understanding more in questions. When there is something become aware trying to ask for that.

As soon as somebody is asking for reusability of parts of coding you are going to touch version management and release management.  The next one will be how can find which version is used where and .... 

That are part of common practice IT governance as also coming in by regulations. I know that is a difficult area for sales and people occupied and locked in with a very technical area.             

It is some kind of humor of ignoring those things. I am associating that with mr Bean.