Technology actions

Technology actions run model scenarios and Data Guru jobs and projects.

Use an Execute App Studio OpenX action to call OpenX API endpoints from within a macro.

  • You must have the Enframe User role to access the Execute App Studio OpenX action.
  • Authentication with the API is handled by the Supply Chain single sign on capability.

Execute App Studio OpenX action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
HTTP Method

Specify the endpoint request type. Choose from the following:

  • GET — endpoints for retrieving data
  • POST — endpoints for sending data
URL Specify the endpoint URI.

Append API query parameters and their values to the endpoint. For example:

/api/v1/app.actions.execute?app_id=myAppID&scenario_id=myScenarioID

If you want to use Supply Chain parameters instead of plain text values, enclose the parameters in curly brackets. For example:

/api/v1/app.actions.execute?app_id={@myAppID}&scenario_id={@myScenarioID}

You can trigger any of the OpenX GET and POST APIs endpoints, but the only response you will receive in App Studio is 200 (success) or 400 (fail). The detailed result set is available in OpenX, and if necessary can be sent back into App Studio using the LLamasoft API Portal.

For more information on OpenX API endpoints, see https://openx-coupa.opexanalytics.com/connector_documentation/#faq.

For more information, see the LLamasoft API Portal.

 

Use a Run Data Flow action to run a Data Flow.

You must be licensed for Data Flows to use this command. If it does not appear in your list of technology actions, see your administrator for access.

Run Data Flow action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Select Data Flow Select the Data Flow that you want to run. If necessary, use the search options to locate the project. The list of Data Flows will include published data flows and data flows created by the user or shared with the user.
Connections Select a connection to use for the data flow. Connection types include models, databases, DDMs, and delimited files (CSV and TXT files). The connections available will depend on the asset type of the data flow's connection.
Parameters

Specify values for any parameters associated with the data flow.

  1. Click .
  2. In the Parameters section, click Add Parameter or Constant.
  3. Specify the session name.

Use a Run Data Guru Project action to run a Data Guru project file.

You must be licensed for Data Guru to use this command. If it does not appear in your list of technology actions, see your administrator for access.

Run Data Guru Project action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Data Guru Project File to execute Specify the Data Guru project file that you want to run. If necessary, use the search options to locate the project.
Use the Data Management page to upload or download Data Guru projects and other assets.
Workflow to run Specify the workflow in the project that you want to run.
Connections

Click the Connections tab to specify any necessary connections.

When you specify a connection, you can also specify the session scope. Choose from the following:

  • Public — run the action using the standard session scope.
  • Private — create a unique session within which copies of all referenced assets are placed, and run the action within it. Private sessions are destroyed automatically when the action completes.
  • Named — run the action in a unique session that is referenced by a specified name. Other macros located in the same app or in different apps and run by the same user or different users can access the named session. Named sessions are persisted until they are destroyed by the End Named Session action.

    If you choose Named, the Scope Name section is displayed. Do the following:

    1. Click .
    2. In the Parameters section, click Add Parameter or Constant.
    3. Specify the session name.
Parameters Click the Parameters tab to specify values for any parameters associated with the project.
Execution History
Execution History

Click Update to check for new logs.

If a log exists, select it to see the details of the run. Successful operations are displayed using green text; errors are displayed in red.

Use a Run DA Model action to run a Supply Chain Guru demand analysis scenario.

Run DA Model action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Design Engine Class Specify the design engine class for the solve and the scenarios included in the run.
Connection Specify a connection to a data source.
Enable Model Diagnostics Specify to run model diagnostics.
Parameter Values tab
Scenario Names Specify the scenario that you want to run. Do the following:
  1. Click .

    A blank field is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.

Use a Run GA Model action to run a Supply Chain Guru greenfield analysis scenario.

Run GA Model action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Design Engine Class Specify the design engine class for the solve and the scenarios included in the run.
Connection Specify a connection to a data source.
Enable Model Diagnostics Specify to run model diagnostics.
Geography Data Connection Name Specify a connection to geography data.
Parameter Values tab
Scenario Names Specify the scenario that you want to run. Do the following:
  1. Click .

    A blank field is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.

Use an Excel Export action to bulk export data to Microsoft Excel from one or more tables or views, including filters. Data can be up to one million rows.

The type of file created depends on the number of records in the table being downloaded: 

  • For tables with less than 100,000 records, an Excel file is generated.

  • For tables with more than 100,000 records, a CSV file is generated.

When a macro with this action is executed, the file is not downloaded right away from the browser. Instead, the user will receive an email with a download link. The downloaded file always have the “Export” file name.

Run Excel Export action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Connection Name Specify a connection to a data source.
Scope Type

Specify the session scope. Choose from the following:

  • Public — run the action using the standard session scope.
  • Private — create a unique session within which copies of all referenced assets are placed, and run the action within it. Private sessions are destroyed automatically when the action completes.
  • Named — run the action in a unique session that is referenced by a specified name. Other macros located in the same app or in different apps and run by the same user or different users can access the named session. Named sessions are persisted until they are destroyed by the End Named Session action.

    If you choose Named, the Scope Name section is displayed. Do the following:

    1. Click .
    2. In the Parameters section, click Add Parameter or Constant.
    3. Specify the session name.
Worksheets Add the appropriate number of worksheets for the export. Specify each worksheet in the Worksheet, Columns, and Advanced sections.
Configure tab > Worksheet section
Name Specify the a name for the worksheet to edit.
Configure tab > Columns section
Add Statement Specify the data to include in the export.
  1. Click Add Statement.

    A blank statement is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.
Add Table Columns Specify multiple columns to include in the export.
  1. Click Add Table Columns.

    The Select A Table And Columns dialog box is displayed.

  2. In the Select a table list, choose the table with the columns that you want to include.

    The columns in the table are listed. By default, all of the columns are selected for inclusion.

  3. Clear the check box for any column that you don't want to include in the grid.
  4. Click OK.

    The specified columns are listed in the statement editor.
Configure tab > Advanced section
Conditions Specify any conditions that must be met to export the data.
  1. Click Add Statement.

    A blank statement is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.
Sort By Filter the data to further narrow the scope of the query. Do the following:
  1. Click Add Statement.

    A blank statement is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.
Only the First __ Records Specify to select only a specified number of records with the highest values.

Use an Excel Import action to import data from Microsoft Excel. This action only appends data to the table without clearing existing data; it does not replace data. Destination tables should be cleared before data is imported. You can use the Delete action for this. Sheet name and column names in the Excel file must match the table/column names in the database.

Run Excel Import action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Prompt Enter the text that you want to display to the user running the macro.
Connection Name Specify a connection to a data source.
Scope Type

Specify the session scope. Choose from the following:

  • Public — run the action using the standard session scope.
  • Private — create a unique session within which copies of all referenced assets are placed, and run the action within it. Private sessions are destroyed automatically when the action completes.
  • Named — run the action in a unique session that is referenced by a specified name. Other macros located in the same app or in different apps and run by the same user or different users can access the named session. Named sessions are persisted until they are destroyed by the End Named Session action.

    If you choose Named, the Scope Name section is displayed. Do the following:

    1. Click .
    2. In the Parameters section, click Add Parameter or Constant.
    3. Specify the session name.
Tables Select the tables where the data should be imported.
Treat empty cell values as

Specify how empty cells are treated. Choose from the following:

  • Null (default)

  • Default (““ for string and 0 for numeric fields)

Use a Run IO Model action to run a Supply Chain Guru inventory analysis scenario.

Run IO Model action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Design Engine Class Specify the design engine class for the solve and the scenarios included in the run.
Connection Specify a connection to a data source.
Enable Model Diagnostics Specify to run model diagnostics.
Run Type Specify the run type. Choose one of the following:
  • Demand Propagation
  • Safety Stock Optimization
  • Infeasibility Diagnosis
  • Service Level Optimization
  • Safety Stock Service Level Optimization
Parameter Values tab
Scenario Names
  1. Click .

    A blank field is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.

Use a Run NO Model action to run a Supply Chain Guru network optimization scenario.

Run NO Model action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Design Engine Class Specify the design engine class for the solve and the scenarios included in the run. If no selection is made, the default version is used.
Connection Specify a connection to a data source.
Enable Model Diagnostics Specify to run model diagnostics.
Disable Core Modeling This parameter is obsolete. It was used to turn off core modeling during the transition from Supply Chain Guru 8 to Supply Chain Guru X.
Parameter Values tab
Scenario Names Specify the scenario that you want to run. Do the following:
  1. Click .

    A blank field is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.

Use a Run NextGen NO Model action to run a Supply Chain Guru network optimization scenario.

Run NextGen NO Model action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Connection Name Specify a connection to a data source.
Scope Type

Specify the session scope. Choose from the following:

  • Public — run the action using the standard session scope.
  • Private — create a unique session within which copies of all referenced assets are placed, and run the action within it. Private sessions are destroyed automatically when the action completes.
  • Named — run the action in a unique session that is referenced by a specified name. Other macros located in the same app or in different apps and run by the same user or different users can access the named session. Named sessions are persisted until they are destroyed by the End Named Session action.

    If you choose Named, the Scope Name section is displayed. Do the following:

    1. Click .
    2. In the Parameters section, click Add Parameter or Constant.
    3. Specify the session name.
Solving Engine

Specify the solving engine version for the solve. If no selection is made, the default version is used.
Resource Size

Specify the level of resources to use for the solve.

  • Enhanced

  • Premium

  • Standard
Select Problem Type

Specify the problem type. Choose one of the following:

  • Network Optimization

  • NO Decomposition

  • Greenfield Analysis

  • NO Infeasibility Diagnosis

  • Cost To Serve Analysis

  • NO and CTS Analysis

  • Rapid Solve
Parameter Values tab
Scenario Names Specify the scenario that you want to run. Do the following:
  1. Click .

    A blank field is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.

Use a Run SIM Model action to run a Supply Chain Guru simulation scenario.

Run SIM Model action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Design Engine Class Specify the design engine class for the solve and the scenarios included in the run.
Connection Specify a connection to a data source.
Enable Model Diagnostics Specify to run model diagnostics.
Cost Data Connection Name Specify a connection to cost data.
Parameter Values tab
Scenario Names
  1. Click .

    A blank field is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.

Tasks are containerized applications created by Coupa. Use a Run Task action to effect models and databases in the Supply Chain cloud.

Run Task action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Select Task Select the task that you want the action to run.
Select Task Version Select a version of the task.
Connections If the task allows you to choose one or more connections to data, specify the connections.
Parameters If the task allows you to provide values for one or more parameters, specify the parameter values.

Use a Run TO Model action to run a Supply Chain Guru transportation optimization scenario.

Run TO Model action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Design Engine Class Specify the design engine class for the solve and the scenarios included in the run.
Connection Specify a connection to a data source.
Enable Model Diagnostics Specify to run model diagnostics.
Parameter Values tab
Scenario Names Specify the scenario that you want to run. Do the following:
  1. Click .

    A blank field is displayed in the Statement Editor.

  2. Construct the query as necessary using the Statement Editor. See Statement Editor Functions for a list of available functions.

Use a Run Model Recipe action to pull DDM data into a Supply Chain Guru new or existing model. A Model Recipe defines what data to pull and how to filter and aggregate the data.

The Run Model Recipe action completion occurs at the completion of the model recipe, so that downstream actions that depend on the recipe being completed can populate the model. Model recipes are available as inputs to macro actions and dynamic views.

Run Model Recipe action properties

Use this property To do this
General tab
Label Specify a name to identify the action on the macro workspace.
Comments Add notes or comments to the action.
Configure tab
Model Recipe Select a model recipe to use.
Create New Model Select this to create a new model rather than overwriting an existing model.
New Model Name If you create a new model, enter a name for the model.
Replace Existing Model Select this to overwrite an existing model.
Connection Name

Select a connection to an existing model to replace.

Last modified: Thursday February 20, 2025

Is this useful?