Setting a Concurrency Limit on Your Map/Reduce Script Deployment in SDF

As part of supporting map/reduce scripts in SuiteCloud Development Framework (SDF), if the scriptdeployments SDF custom object XML definition in your SuiteCloud project specifies a concurrency value that exceeds the limit available in the target account, the concurrency limit value is adjusted to the account limit when your project is deployed to the account.

If the account concurrency limit increases in your target account, the concurrency value limit is updated when the source value is larger. This happens automatically to the map/reduce record that was deployed through SDF. Adjustment by SDF no longer occurs when the concurrency field of deployment record is edited from another context such as the UI.

For example, if you set concurrency value to 10 in your map/reduce object and deploy the SuiteCloud project to an account with a concurrency limit of 5, the deployment record in the account is set to 5. If you then download the map/reduce object as XML or import it to a SuiteCloud project, the concurrency value is unchanged. It remains set to 10.

The following example shows a Map/Reduce script deployment with a concurrency limit of five:

<mapreducescript scriptid="customscript_mr">
    ...
    <scriptdeployments>
        <scriptdeployment scriptid="customdeploy_123">
            <title>My Script Deployment</title>
            <isdeployed>T</isdeployed>
            <loglevel>AUDIT</loglevel>
            <runasrole></runasrole>
            <status>NOTSCHEDULED</status>
            <concurrencylimit>5</concurrencylimit>
        </scriptdeployment>
    </scriptdeployments>
    ...
</mapreducescript>

For more information, see the following topics:

• scriptdeployment

• mapreducescript

• Concurrency Limit