Business Process Server resource hierarchy

The authorization process in Business Process Server is performed by the ACLManager. Actions are placed on the resource. The list of resource/action pairs associated with the user/group represent that user/group’s privilege. Actions define the type of task you can perform on the resource.

Business Process Server

Process instance resources. This hierarchy gives a user the right to perform operations on a process instance, i.e. BPServer.PI.Approval.App#1, while another user has the right to perform operations on BPSever.PI.Approval.App#2. Remember, a user with the right to perform operations on BPServer.PI.Approval as a resource inherits the right for all instances of Approval. Likewise, a user with the right to perform an operation on BPServer.PI, may perform that operation on all Business Process Server process template instances.

Dataslot resource. Consider the protection for the "salary" and "resume" dataslots of the Hiring#1 process instance. The resource names are BPServer.DS.Hiring.Hiring#1.salary and BPServer.DS.Hiring.Hiring#1.resume. A user with the rights to resource BPServer.DS.Hiring.Hiring#1 has the rights on all Hiring#1 dataslots, which includes "salary" and "resume."

Process template resource. The shallowest of the Business Process Server hierarchies, this permission allows defining process templates as resources. Any template, such as Approval, Hiring or Timeoff can be protected as a resource in Business Process Server. You may reference these templates as BPServer.PT.Approval, BPServer.PT.Hiring, or BPserver.PT.Timeoff.

Table 47. BP Server resources
Type	Name
Process Template	PTName
Process Instance	PTName.PIName
Data Slot	PTName.PIName.DSName

BPM Events

Table 48. BPM Events resources
Type	Name
Infopad	infopadname

Management

Table 49. Management resources
Type	Name
Report	PTName.reportName
BPMSQLReport	fileName
ReportBuilder	reportTypeThe Report Types are: OEBPS. Internally created reports in the Management module. External. Reports from external reports sources, crystal, BPM SQL, etc.

Administration

Table 50. Administration resources
Type	Name
Application	appName
Modeler	modelername
Configuration	conffilename
Queue	queuename
Reusable Components	reusablecomponentName
Log	componentName
Server	servername
Group	groupname
User	username
Permission	permission¹

¹ This is a general, not a specific permission for this resource. You may name this permission anything but "mypermission."

Dashboard

Table 51. Dashboard resources
Type	Name
Dashboard Component	componentname

Actions

Actions are the type of task you can perform on the resource. For example, you may grant a permission to a group to start and stop a server in the Administration module. The resource is the server, stop and start are the actions, and Administration is the component. Unlike resources, actions are not hierarchical. The following table depicts all actions defined for all Business Process Server resources:

Table 52. Actions for resources
Component	Resource type	Actions
BP Server	Process instance	Any, Remove, Suspend, Resume, View, Update
BP Server	Process template	Any, View, Update
BP Server	Dataslot	Any, View, Update
BP Server	Infopad	Any, View, Update
Management	Report	Execute
Management	BPMSQLReport	Execute
Management	ReportBuilder	Any, Create, Update, Remove
Administration	Server	Any, Start, Stop, Suspend, Resume, View Status
Administration	Configuration	Any, View, Update
Administration	User	Any, View, Create, Remove, Update, Delegate
Administration	Group	Any, View, Create, Remove, Addmember, Removemember, Change Role, Update
Administration	Application	Any, Install, Uninstall, Suspend¹, Resume1, Publish, Unpublish, Execute²
Administration	Queue	Any, View, Create, Remove, Addmember, Removemember, Update
Administration	Reusable Component	Any, Import, Export, Delete
Administration	Log	Any, View
Administration	Permission	Any, View, Create, Remove
Administration	Modeler	Any, View, Create, Update, Remove
Dashboard	Dashboard Component	View

¹ You cannot suspend and resume a Web application.

² The execute action protects a Web application from unauthorized execution. For example, in the Start step of the Web process, if an authenticated user is not authorized to execute the application, then they will receive an authorization failure error.