BookmarkSubscribeRSS Feed

Self explanatory

5 Comments
PhilC
Rhodochrosite | Level 12

Enterprise Guide generates macro variables like these examples in a program node already:

%LET _CLIENTTASKLABEL='50 macro _review_14c';

%LET _CLIENTPROJECTPATH='C:\COS11\SAS Code Group II-recA.egp';

%LET _CLIENTPROJECTNAME='SAS Code Group II-recA.egp';

I am suggesting that a macro variable like this example also be added by Enterprise guide:

%LET _CLIENTPROCESSFLOWLABEL='14.c Review';

CaseySmith
SAS Employee

Thanks for the suggestion!  Makes sense.  I went ahead and added it.  It will be available in a future release.

Note: I added _CLIENTPROCESSFLOWNAME (NAME, rather than LABEL), since that is the more common way we refer to process flows.  We used LABEL in _CLIENTTASKLABEL, since "task name" could cause some confusion with a task name (ex. "List Data task") versus the label for an instance of that task.

PhilC
Rhodochrosite | Level 12

Super, can't wait to see it work.

bheinsius
Lapis Lazuli | Level 10

It looks like this was added in EG 7.12, as _CLIENTPROCESSFLOWNAME:

 

2016-08-10_10-56-49.png

 

Casey_SAS
SAS Employee
Status changed to: Suggestion Implemented

Enterprise Guide 7.12 and higher have the _CLIENTPROCESSFLOWNAME The name of the process flow as the macro variable