Working with Privileges → About Privileges → Privilege Examples for Publishing and Deploying
Audience: On-premise.
This topic provides examples of the privileges required for designers who create and publish process apps, and for a managed administrator who deploys those process apps.
Pauline, a process app designer, has the requirements that she needs to create a new Issue Tracking process app in SBM Composer. She completes a prototype and checks a public version in to the repository. She will not deploy the process app to a runtime environment, but will ask Robin, a managed administrator, to do so at a later time.
Privilege Type | Privileges | Granted in |
---|---|---|
Repository | None, however, when Pauline publishes the
process app for the first time, she is automatically granted the following
privileges:
|
SBM Application Repository |
Deployment | None, since Pauline will only check in the process app from SBM Composer, but will not deploy it to a runtime environment. | N/A |
Administrative | None, since Pauline will not log in to SBM Application Repository or configure the deployed application. | N/A |
Alex, a co-designer with Pauline, needs to modify the Issue Tracking process app prototype. Once he does so, he needs to publish the process app so that Pauline can check out the updated process app.
From SBM Composer, he tries to open the process app from the repository so he can make his modifications. Alex gets an error message saying that he does not have the privileges required to view process apps in the repository.
Robin, a managed administrator, logs in to SBM Application Repository and grants Alex the privileges he needs to view and open the process app. Alex opens the process app in SBM Composer, makes his changes, and then publishes the process app. He then informs Pauline that an updated version is in the repository.
Privilege Type | Privileges | Granted in |
---|---|---|
Repository |
|
SBM Application Repository |
Deployment | None, since Alex will only check in the process app from SBM Composer. | N/A |
Administrative | None, since Alex will not log in to SBM Application Repository or configure the deployed application. | N/A |
Robin, a managed administrator, receives a request from Alex and Pauline to deploy the Issue Tracking process app to the test environment. Robin logs into SBM Application Repository, and then deploys the process app to the SBM Application Engine server used as the test environment.
Privilege Type | Privileges | Granted in |
---|---|---|
Repository | View and Deploy for the Issue Tracking process app | SBM Application Repository |
Deployment |
|
SBM Application Administrator |
Administrative (with Managed Administration product access) |
|
SBM Application Administrator |
Robin decides that for testing, Pauline and Alex can deploy process apps directly from SBM Composer to the test environment. Pauline and Alex are glad that they can now deploy the latest revision of the Issue Tracking process app without waiting for someone else. Pauline updates the process app, and then from SBM Composer, she deploys it.
Privilege Type | Privileges | Granted in |
---|---|---|
Repository | View, Edit, and Deploy for the process app | SBM Application Repository |
Deployment |
|
SBM Application Administrator |
Administrative (with Managed Administration product access) |
|
SBM Application Administrator |
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.