MNG Engine (Engine mng)

This engine provides jobs for managing groups and users of enaio®.

The following jobs can only be executed by users with administrator rights:

4. Security System

The security system has two mechanisms that operate side by side in the same system: clauses at the group level (see mng.ExportSecuritySystem) and ACL rules at the object level (see dms.ReadSD and the other DMS security jobs).

5. Language Resources

5.1. JSON Schema

The methods mng.GetResourceString, mng.SetResourceString and mng.DeleteResourceString support input and output parameters in JSON format. For JSON tags, case sensitivity is observed. For the content of language abbreviations and keys, case sensitivity corresponds to the database setting.

Keys beginning with OS, RichClient or WebClient are reserved and must not be changed. Own keys must be created in the Project area.

The JSON schema for all three methods:

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "type": "object",
  "properties": {
    "Keys": {
      "type": "array",
      "items": [{
        "type": "object",
        "properties": {
          "Key": { "type": "string" },
          "Lang": { "type": "string" },
          "Values": {
            "type": "array",
            "items": [{
              "type": "object",
              "properties": {
                "Lang": { "type": "string" },
                "Value": { "type": "string" }
              },
              "required": ["Value"]
            }]
          }
        },
        "required": ["Key"]
      }]
    }
  }
}

Example for mng.SetResourceString (input) and mng.GetResourceString (output):

{
  "Keys": [
    {
      "Key": "Project.key1.Workflow_3",
      "Values": [
        { "Lang": "en_US", "Value": "Bill" },
        { "Lang": "de_DE", "Value": "Rechnung" }
      ]
    }
  ]
}

Example for mng.GetResourceString and mng.DeleteResourceString (query parameters):

{
  "Keys": [
    { "Key": "Project.key1.Workflow_3", "Lang": "en_US" },
    { "Key": "Project.key2.*", "Lang": "de_DE" },
    { "Key": "Project.key3.*", "Lang": "*" }
  ]
}

mng.GetUserRoles returns the system roles assigned to a user in the output parameter Result as a semicolon-separated list of IDs. The following overview describes all possible roles, grouped by component.

5.2. DMS

ID System Role

18

DMS: Supervisor

66

DMS: Set up local security groups

5.3. Administrator

ID System Role

1

Administrator: Start

2

Administrator: Configure entire system

4

Administrator: Configure security system

5

Administrator: Configure W-templates

6

Administrator: Configure archive print

8

Administrator: Start automatic actions

9

Administrator: Configure automatic actions

10

Administrator: View user trays

50

Administrator: Edit object rights

65

Administrator: Configure local security groups

5.4. Editor

ID System Role

11

Editor: Start

12

Editor: Edit object definition

13

Editor: Customize database

96

Editor: Define visibilities

5.5. Start / Capture

ID System Role

14

Start: Start

15

Capture: Start

16

Capture: Configure

87

Capture: Edit filing tray

5.6. Client

ID System Role

17

Client: Save personal settings

19

Client: Use workflow

28

Client: Open history

29

Client: Start expert mode

30

Client: Export document contents

31

Client: Edit notes

32

Client: Recover data from history

33

Client: Show personal recycle bin

34

Client: Run SQL queries

35

Client: Send content as e-mail

36

Client: Start

37

Client: Show system recycle bin

38

Client: Edit SQL queries

39

Client: Manage subscriptions

40

Client: Delete objects from recycle bin

44

Client: Open properties

45

Client: Debug events

49

Client: Create events

51

Client: Use object search

52

Client: Use navigation

53

Client: Delete archived documents

55

Client: Manage follow-ups

56

Client: Configure history for individual object

57

Client: Execute changes in batch mode

59

Client: Add icon

60

Client: Delete icon

61

Client: Workflow substitute configuration

62

Client: Workflow process administration

63

Client: Move objects

64

Client: Edit static layers of other users

67

Client: Edit workflow circulation slip

68

Client: Manage private circulation slip templates for workflows

69

Client: Manage public circulation slip templates for workflows

71

Client: Open notes

73

Client: Always show variant administration

74

Client: Print documents

75

Client: Change archiving status

76

Client: Show favorites

77

Client: Customize ribbon

78

Client: Run default search

79

Client: Move across cabinets

80

Client: Configure external applications

81

Client: View preview annotations

82

Client: Edit preview annotations

83

Client: Assign further locations

84

Client: Create reference documents

85

Client: Share documents

86

Client: Manage sharing options

89

Client: Clients

90

Client: Show workflow substitutions

91

Client: Follow-ups for others

92

Client: Subscriptions for others

93

Client: Manage public desktop

94

Client: Scan documents

95

Client: Show number of objects in register tree

97

Client: Export index data

98

Client: Undo the checkout for others

99

Client: Open links

100

Client: Edit links

102

Client: Copy across cabinets

108

Client: Manage workflow absences

110

Client: Use subscriptions

111

Client: Use follow-ups

5.7. WebClient

ID System Role

70

WebClient: Start

101

Webclient: Open location

103

WebClient: Use saved searches

104

WebClient: Use object references

105

WebClient: Use subscriptions

106

WebClient: Use follow-ups

107

WebClient: Show history

5.8. Workflow

ID System Role

20

WF-Admin: Start

21

WF-Editor: Start

22

WF-Editor: Edit organization

23

WF-Editor: Create model

24

WF-Processes: Start via import

25

WF-Simulation: Start

26

WF-Script: Start

58

WF-Editor: Report presence/absence of users

5.9. Enterprise-Manager

ID System Role

27

Enterprise-Manager: Start

5.10. Server

ID System Role

72

Server: Switch job context

88

Server: Execute Ado jobs

109

Server: Execute script