Preferences

You can use the Preferences page to set a broad range of preferences including:

To change a preference:

  1. Click the Apps menu, select an app, and click on the icon under Actions.
  2. Click Configurations, and then click the Preferences tab.
  3. Select the preference type.
  4. Make your changes to the preferences and click Save.

Design preferences

Transaction – data review process

Select the workflow to be used for the Data File review.

Workflow Description
Defined by Developer The program developer specifies the data review process.
No Data Review Process The data that was entered in Transaction does not require a review.
Review and Post - One Step One person enters the data, and the Reviewer reviews and then posts the data. The Reviewer then becomes the person of record for entering the data.
Review and Post - Separately The Reviewer reviews the data, and then returns the data to the Runner who posts the data.
Custom The Custom Workflow can be added to the solution after the Data Template is submitted to the library.
Add a Reason for Data File Rejection If this option is checked, Reviewers must include a reason for any file rejection in the Comments area.
Note:

The Add a Reason for Data File Rejection option is not applicable to the Custom Data File Review process. For this process, the properties defined for the Approval node will be respected.

Transaction – run configuration

The Data File is posted to SAP after it is approved for use in production. These settings do not apply to the Custom Data File Review Process.

Setting Description
Defined by Developer The Program Developer specifies which transaction run configuration applies.
Manual Only a manual run configuration is allowed.
AutoRun Only an AutoRun configuration is allowed.
Run Credentials
  • Reviewer/Originator: The Reviewer/Originator user does the posting.
  • System Account: The user specified in the System Account drop-down list does the posting.

Query and transaction approval settings

Specify the approval requirements for solution workflows.

Setting Description
Solution Approval Indicates whether Query or Transaction Solutions require approval. If this setting is not active, solutions move immediately to production status upon submission – no review is required.
Self Approval Allows Query/Transaction file creators to approve their own files.
Reason for Solution Rejection Indicates whether Reviewers must provide a reason for rejecting the Query or Transaction solution. Make this option Active to require a reason for solution rejection.

Form Approval Settings

Specify the approval requirements for form workflows.

Setting Description
Form Approval When set active, Solution Developer will only be able to develop and save a Solution but not deploy it. If Solution developers try to deploy the solution, they see an error message. Solution Reviewer can only review and deploy a Solution, but cannot make any changes to it.

Version control

Specify the version control settings for Data Templates.

Setting Description
Version Control for Data Templates Restricts users from opening or submitting a data file which was created with an older version of the data template.To note: When revising a data template using the Version Control for Data Templates feature, users must retain the same data template name.
Revision of Data Templates Enables users to select Revise in the Submission Wizard. By default, to resubmit a revised data file, users must also resubmit the Transaction script.

Query script creation settings

Select settings that impact the Query script creation process.

Setting Description
Centralize Query Data Dictionary Usage Provide one data dictionary for all users. Only the Query data dictionary administrator may add tables. See below for further information.
Users Manage the String Padding in Criteria Padding (also known as “leading zeros”) is applied by default for NUM, NUMC, Char, and string data types. If you compare non-numeric data without padding, the results may not be accurate. Activate this setting to enable string padding.
Users Create SQL Server Connections in Query Query designers use the SQL Server connections defined on the Evolve site. They can also create their own connections to SQL Server – connections which are specific to the Query script. If this setting is not active, Query designers can use only those SQL Server connections already defined on the Evolve site.
furtherinformation:

Further information: With a centralized dictionary, users can still assign favorites from the existing tables, but these local favorites are not written to the server. A Query data dictionary administrator can create or edit a dictionary and upload it to the Evolve Server.

This administrator can also edit a local copy or download the latest copy from the server. They can search for and add tables within both the Winshuttle data dictionary and the SAP data dictionary.

To apply a centralized data dictionary, you must be a Query Data Dictionary Administrator for the app. This administrator is assigned from the Edit Apps page. You must have both the Solution Developer and Query Data Dictionary Administrator role to use this feature.

Capabilities

On this page, Global Admins and App Admins can enable or disable the capabilities of script/solution creation (and running of scripts) on the application level. If a capability option (Transaction, Query, or Direct) is disabled, that app will not have the script creation or run capabilities of that type, even if you have a valid and applicable license and permissions.

Capability Description
Transaction Enable or disable the creation of Transaction Solutions
Query Enable or disable the creation of Query Solutions
Direct Enable or disable the creation of Direct Solutions
Note:

The changes are affected only after you switch apps or re-log in to Studio.

If you have a template that includes a Query script with an embedded Transaction script, you can submit the solution even if you do not have the capability to submit Transaction solution files.

Run preferences

  1. General Settings Settings related to the way files are run on SAP.
    Setting Description
    Save to Library If files do not require a review, you can save them to the Evolve server. Please note that when saved, files not requiring reviews are automatically placed in the Complete state.
    Enable Adaptive Query Throttling When set to active, Adaptive Query Throttling uses an algorithm to adapt and adjust the execution of the query on the SAP server; the adjustment is based on the load on the SAP server at the time of execution. Further information: Available server resources are calculated from the total number of open dialog processes. When greater than 50 percent of the dialog processes on the SAP system are available, the query is executed at full speed. When the available server load falls below 50 percent, the execution of the query is dynamically slowed.
    Add a Reason for Transaction Script Run When set to active, this setting requires a reason to be provided before a Transaction script may be run.
  2. Scheduling Scheduling allows you to manage how Query and Transaction script schedules are established.
    Setting Description
    Transaction Script through Desktop Scheduling Set to active, this allows desktop scheduling for Transaction scripts.
    Schedule with Changed Settings Set to active, this enables settings which are changed in a file to overwrite settings in the recorded script.
    Query Script through Desktop Scheduling When set to active, desktop scheduling for Query scripts of the following types is allowed.
    • Excel
    • XML
    • Access
    • Text
  3. Run Options Panel The Run Options Panel is where you specify the way advanced run settings are made available to Runners.
    Setting Description
    Back up SAP Data When this is set to active, Runners see the checkbox for Back-up SAP Data checked by default in Studio.
    Run only Unprocessed Rows When this is set to active, Runners see the checkbox for Run only Unprocessed Rows checked by default in Studio.
    Production Server Warning on Run When this is set to active, Runners see the checkbox for Production Server Warning on Run checked by default in Studio.

Developer proficiency level

Use the Developer Proficiency Level page to set a proficiency level for Query developers. The Developer Proficiency Level is assigned when creating a new user. Proficiency levels include the following:

  • Basic
  • Standard
  • Advanced

Each proficiency level includes setting elements related to user capabilities. To update these settings:

  1. Check a box to enable any of the features below; clear a box to disable them.

    • Enable User Creation of Joins in Query Builder
    • Cluster, View, and Pool Table Joins with another transparent Table
    • Enable Query Script Creation Based on Infoset/Queries Data Source
    • Enable Left Outer Joins
    • Enable Manual Join Creation between Mismatched Fields (Advanced only)
  2. In the Maximum number of tables in Query field, type a number. (By default, basic proficiency level users are limited to 2; Standard to 4; Advanced to 9. The maximum allowable number is 25.)
  3. Click Save.

System usage levels

System usage levels indicate the level of system resources a query can consume during execution. You can use the System usage levels page to define extraction settings for each system usage level.

You can designate low, medium, or high system usage levels. Each level includes the following options:

  • The length of the time-out
  • The maximum number of result rows

When a query is submitted for review, the Developer specifies a usage level anticipated for that query. The query Reviewer can change the usage level setting if necessary.

Note:

An approved query will not run if its system usage level does not match the level designated in the server policy for the server where it will run.

System Usage Levels Description

Low

The SAP system has low usage and there are sufficient available resources. Use this setting if you are comfortable with the Query using a high level of resources and returning a large data set. You can set the Query time-out to a high number and there can be an unlimited number of returned Query results.

To note: If you submit a Query marked with a High system usage level when the administrator has specified that only Low system usage levels are allowed, the query file will not run.

Medium

The SAP system has medium system usage level and requires moderate resources. Use this setting if you are comfortable with the Query using a moderate amount of resources and returning a large data set. You can set the Query time-out to a moderate number and there can be a high number of returned Query results.

High

The SAP system has a high usage level and resources are constrained. Use this setting if you want to limit Query to a minimal amount of resources and to returning small data sets. The Query timeout and results can be set to a low number.

Change system usage levels

  1. For each system usage level you edit, set the following options:
    • The length of the time-out, in seconds
    • The maximum number of row results. Enter a number in the field or click No Limit
  2. Click Save.

Authorization fields

Use the Authorization Fields page to review, add, edit, and/or delete authorization fields.

Add fields

  1. On the Authorization Fields page, click Add.
  2. Provide the Table Name, Authorization object, Field, Field Text, and Authorization Text information, as needed.
  3. Click Save.

Edit fields

  1. From the Authorization Fields list, select the field you need to edit.
  2. Click Edit.
  3. Make changes to the Table Name, Authorization object, Field, Field Text, and/or Authorization Text fields, as needed.
  4. Click Save.

Delete fields

  1. From the Authorization Fields list, select the field you need to delete.
  2. Click Delete.
  3. When prompted to confirm the deletion, click Yes.