Extending Control (from Fraktal SAS Programming): Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
K |
K |
||
| Zeile 16: | Zeile 16: | ||
* [[Workflow Documentation (from Fraktal SAS Programming)|Workflow Documentation: Document workflow by writing comments to the LOG]] | * [[Workflow Documentation (from Fraktal SAS Programming)|Workflow Documentation: Document workflow by writing comments to the LOG]] | ||
* [[Realtime Information (from Fraktal SAS Programming)|Realtime Information: Inform responsibles about invocation by sending an email]] | * [[Realtime Information (from Fraktal SAS Programming)|Realtime Information: Inform responsibles about invocation by sending an email]] | ||
| + | |||
We will implement these requirements now step by step and thereby touch relevant parts of the '''so-called ''SAS Macro Facility'''''. | We will implement these requirements now step by step and thereby touch relevant parts of the '''so-called ''SAS Macro Facility'''''. | ||
Version vom 13. Mai 2014, 15:00 Uhr
|
|
|
|
Now, with proper declaration, it is safe to run your MACRO as a component in a validated system. However, it is still difficult to follow its results and discover failure risks or un-wanted misbehavior.
You might therefore find it useful to add functionality such as:
- Apply Logic: Check, branch and loop for specified parameters’ values
- Process Metadata: Navigate through the ecosystem by reading and processing metadata
- Workflow Documentation: Document workflow by writing comments to the LOG
- Realtime Information: Inform responsibles about invocation by sending an email
We will implement these requirements now step by step and thereby touch relevant parts of the so-called SAS Macro Facility.
|
|
|
|
