Administrator's Guide

Transcription

1 Administrator's Guide EPMWARE Version 1.0 EPMWARE, Inc. Published: July, 2015

2 Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of EPMware Inc. EPMware, Inc. may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from EPMware, Inc., the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property EPMWARE, Inc. All rights reserved EPMWARE is a registered trademark of EPMWARE, Inc. in the United States and/or other countries. All other trademarks are property of their respective owners.

3 Contents Administrator's Guide... 1 Contents... 3 Introduction... 5 Configuration... 6 Infrastructure... 6 Servers... 6 Databases... 8 Applications Applications Configuration Applications Properties Dimensions Dimension Configuration Dimension Properties Dimension Mapping Properties Property Mapping Property Validation Property Derivation Templates Global Settings Settings Application Settings Web Settings User Defined Settings Lookups Security Security Model Security Rules Roles Requestor Reviewer Approver... 45

4 Default Users Groups Security Classes Security Provisioning Modules Workflow Workflow Tasks Workflow Builder Workflow Stages Deployment Deployment Manager Deployment Monitor Monitor Grid Deployment Status Status Legend Deployment Schedule Logic Builder Logic Builder Editor Services ERP Import EPR Import Builder EPR Import Mapping Header Section ERP Import Monitor

5 5 Introduction EPMware is a master data management and workflow tool that manages master data and enforces your organization s workflow around the everyday processes that surround your metadata changes. By configuring shared dimensions in EPMware, users request metadata once and our workflow engine routes the request to obtain approvals and deploys the metadata to the participating target systems. This allows standardization and rationalization of your metadata to evolve as your organization develops its master data strategy. The EPMware dashboard allows users, managers, and application administrators to monitor the status of metadata requests in real time. Follow a request from the initial Create stage through its Review, Approve and Deploy stages. A graphical representation of each request's status in the workflow allows users to identify any bottlenecks in the metadata request process and determine if an escalation is required. Seamless integration to Hyperion EPMA, Classic Hyperion Financial Management (HFM), Classic Essbase and Classic Planning applications allows EPMware to deploy metadata without manual intervention or file manipulation from an administrator. Approved metadata is automatically deployed or scheduled for deployment using our built in scheduler. One-click import of your target system hierarchies allows users to clearly visualize how metadata will appear in their production environments. A configurable security module integrates with your current LDAP or Microsoft Active Directory (MSAD). Build, maintain and scale task driven workflows. Administrators model, build and maintain fully dynamic and scalable workflows using the Workflow Builder. By using a combination of stages and tasks, Workflow Builder enables creation of any number of workflows that visually define your organization s business process, and then enforces it. The Workflow Builder includes reusable workflow tasks, rule based validations, exception handling, notifications for all workflow stages, custom functions and scripting for limitless customizations. Centrally manage metadata deployments using the EPMware deployment module. It manages how and when metadata requests are deployed. Load metadata on demand or schedule a batch to run during off hours. Deployment metrics for all your EPM applications are on one page. Monitor in real time as one time or batches are deployed to their respective target applications. Create a recurring calendar for daily, weekly or monthly metadata deployments. Audit reports log every transaction, sign-off & deployment. EPMware maintains a complete audit trail of all transactions from request to deployment. Every transaction can be queried using reports included in the Audit module.

6 6 Configuration The configuration module is used by the Administrator for the initial configuration and the ongoing administrative tasks of EPMware. The Configuration module is comprised of the following components: Infrastructure Applications Dimension Property Misc Infrastructure Servers Server Configuration enables the administrator to enter the Server Names, User ID s, Passwords and Descriptions that EPMware will use to communicate with the target systems (e.g. HFM, Essbase, Planning). By default, this page will initially render blank until a row is added. To Add a Server 1. Select the icon to display the Add Server popup box. 2. Input Server Name, User Name, Password and Description (Optional) 3. Select Save to add the server to the Server Grid.

7 7 To Edit a Server 1. Right click on a row and select Properties from the Menu to display the Server Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

8 8 To Delete a Server 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Server. Note: Only one Server can be deleted at a time. Databases Database Configuration enables the administrator to enter the Database Names, User ID s, Passwords, TNS entries and Descriptions for the target databases that EPMware will use to connect to (EPMA, HFM, Planning, etc). By default, this page will initially render blank until a row is added. To Add a Database 1. Select the icon to display the Add Database popup box. 2. Input Database Name, User Name, Password, TNS entry and Description (Optional)

9 9 3. Select Save to add the database to the Database Grid. To Edit a Database 1. Right click on a row and select Properties from the Menu to display the Database Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

10 10 To Delete a Database 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Database. Note: Only one Database can be deleted at a time.

11 11 Applications Applications Configuration defines a target application. The grid will be blank until an initial row is added. The Upload button in the row will be grayed out until the record is saved. Application Configuration had two Tabs, Configuration and Properties. The Configuration Tab contains all the general application information. The Properties Tab contains detailed properties for the application. Note: Select the Enabled check box in the Grid to enable the Application and select to save the change. Applications Configuration To Add a Target Application 1. Select the icon to display the Add Application popup box. 2. Input or select the following fields: Application Name - User defined name for the application. Target Application - Input target application name. Application Type - Select target application type. Version - Selects the target application version. Security Class Select a Security Class defined during security class configuration. Deployment - Select Deployment Method: Direct, File, Interface Tables.

12 12 Server Name - Select a Server defined during Server configuration. Database Name - Select a database defined during Database configuration Target User Name - Input the target application user name. Target Password - Input the target application password. To Import an Application 1. Select the icon in the Grid to import the application and display the Application Import popup box.

13 13 2. Select Auto Import to import the Application from the Target Application Server or select Manual Import to Browse for a file to import. Essbase (Classic) o Manual Import.xml formatted file Run the following script in EAS to generate the.xml file: Export outline ASOALL.Basic all dimensions to xml_file "c:/temp/asoall02.xml"; Planning (Classic) o o Auto Import Manual Compress the following files using WinZip Create one.csv file for each dimension using the Essbase Outline Load Utility LCM extract file HFM (Classic) o Manual Import.xml formatted file Use Metadata Extract from the HFM Application EPMA Application o o Auto Import Manual Import Compress the following files using WinZip LCM Export file system

14 14 3. The Application Progress Bar will display while the Import is running. 4. The Application Hierarchy Import Status popup will display when the import is completed. Note: Click the popup. icon in the Grid to redisplay the Application Import Status Note: If the Application Import is still running, the Cancel Import and View Progress Bar buttons will be available on the Application Import Status popup.

15 15 To Edit an Application 1. Right click on a row and select Properties from the Menu to display the Application Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

16 16 To Delete an Application 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Application. Note: Only one Application can be deleted at a time.

17 17 Applications Properties To Add a Property 1. Select the icon to display the Add Properties popup box. 2. Input the Property Name, Property Value and Description. 3. Select Save to save the record. To Edit a Property 1. Right click on a row and select Properties from the Menu to display the Application Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

18 18 To Delete a Property 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Property Note: Only one Property can be deleted at a time. Dimensions Dimension configuration defines dimensions imported from the target application and how they will be managed in EPMware. Dimensions can be enabled and disabled, assigned Security a Class, and alternate Dimension Labels can be assigned.

19 19 Dimension Configuration Select and Application from the dropdown list to view the Dimensions. Grid Columns Dimension - List of dimensions imported from target application. Security Class - Assigns Security Classes to the Dimension Enabled- Enable or Disable the Dimension in EPMware Description - User defined description. To Assign a Security Class 1. Double click in the Security Class field and select a Security Class from the dropdown list. 2. Select to save the changes. To Edit a Description 1. Double click in the Description field to switch to edit mode and edit the Description. 2. Select to save the changes.

20 20 Dimension Properties Select an Application and a Dimension from the dropdown lists to view the Properties for the Dimension. To Add a Property 1. Select the icon to display the Add Dimension Properties popup box. 2. Input the Property Name, Property Value and Description. 3. Select Save to save the record.

21 21 To Edit a Property 1. Right click on a row and select Properties from the Menu to display the Dimension Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes. To Delete a Property 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Property. Note: Only one Property can be deleted at a time.

22 Dimension Mapping Dimension Mapping enables a Dimension in one Application to be associated with a Dimension in another application. A Dimension is selected in a row, and mapped to an associated Dimension in another Application. The Mapping can be Enabled or Disabled by selecting the check box and selecting to save the record. The column headers will display all Active Applications in EPMware. Double click on the Dimension column field to display a dropdown list of all active Dimensions for that Application. 22 Note: A minimum of two Dimension column values must be selected before the row can be saved. Caution: Dimension Types must match if two application columns are of type EPMA and the Dimensions are Shared in the EPMA Dimension Library. Note: A row in the Line Item Grid on the Request Page will be created for each application Dimension that is configured with Sync, including EPMA applications using the Shared Library. The properties for EPMA applications using the Shared Library can be overridden with different properties for individual applications. If properties are changed for an individual application and the application is an EPMA application using the Shared Library, the properties for the other applications using

23 23 the Shared Library will be exported to EPMA as an Override. To Create a Dimension Mapping 1. Select the icon to add a row to the top of the grid 2. Input a Dimension Label 3. Double click on the Dimension Field below the First application to be Mapped and select a Dimension, then double click on the Options Field and select Sync or select a Script. 4. Double click on the Dimension Field below the Next application to be Mapped and select a Dimension and double click on the Options Field and select Sync or select a Script. 5. Click to Save the row. Dimension Mapping Example for mapping the Measures Dimension for BSO Demo Classic and the Accounts Dimension for the BSOALL Application. Note: The selection for the Options Column must be the same for the Mapped Dimensions. Caution: The new row or changes will not be committed to the database until the Save icon is selected. After saving, the rows are automatically resorted alphabetically.

24 Properties Property configuration defines how Properties are Mapped, Validated, and Derived between Applications and Dimensions in EPMware. A Property map can be created for any Dimension that is mapped in EPMware. Property Map definitions can be enabled and disabled and alternate Dimension Labels can be assigned. Properties for EPMA applications and Classic applications can also be shared. 24 Property Mapping When a Property is mapped it will automatically populate the corresponding shared properties in the other applications and dimensions. The Reviewer of the corresponding application that is sharing the property has the option to change the property. The property will appear in EPMA as an override. The column headers will display all Applications associated with the selected Dimension. Double click on the Property column field to display a dropdown list of all Properties for the Dimension. Note: A minimum of two Property column values must be selected before the row can be saved. Caution: Property Types must match if two application columns are of type EPMA and the Dimensions are Shared in the EPMA Dimension Library. Note: A row in the Line Item Grid on the Request Page will be created for each application Dimension that is configured with Sync, including EPMA applications using the Shared Library. The properties for EPMA applications using the Shared Library can be overridden with different properties for individual applications. If properties are changed for an individual application and the application is an EPMA application using the Shared Library, the properties for the other applications using

25 25 the Shared Library will be exported to EPMA as an Override. To Create a Property Map 1. Select the icon to add a row to the top of the Grid 2. Input a Property Label 3. Double click on the Property Field below the First application to be Mapped and select a Property, then double click on the Options Field and select Sync or select a Script. 4. Double click on the Property Field below the Next application to be Mapped and select a Property and double click on the Options Field and select Sync or select a Script. 5. Click to Save the row. Property Mapping Example for mapping the Consolidation Property for BSO Demo Classic and the Consolidation Property for the BSOALL Application. Note: The selection for the Options Column must be the same for the Mapped Dimensions. Caution: The new row or changes will not be committed to the database until the Save icon is selected. After saving, the rows are automatically resorted alphabetically. Property Validation Property Validations provide a validation for a property in addition to the standard validations inherent to the application. Property Validations are created at ConfigurationPropertyValidations.

26 26 To Create a Property Validation 1. Select the icon to display the Create Property Validation popup box. 2. Select the Application Name 3. Select the Dimension Name 4. Select the Property Name 5. Select a Validation Script 6. Enable or Disable the Property Validation 7. Input a Description 8. Select Save to save the record.

27 27 Note: All Scripts are created and managed in the Scripts Module. To Edit a Property Validation 1. Right click on a row and select Edit Properties from the Menu to display the Edit Property Validation popup box. 2. Edit the properties as required. 3. Select Save to save the changes. To Delete a Property Validation 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display

28 28 3. Select OK to delete the Property Validation. Note: Only one Property Validation can be deleted at a time. Property Derivation Property Derivation provides a method of deriving a property value from a Script. Property Derivations are created at ConfigurationPropertyDerivations. A Derivation Script must be created in the Scripts Module to define the Property Derivation. The Script can then be selected in the Script Name column. To Create a Property Derivation 1. Select the icon to display the Create Derivation popup box. 2. Select the Application Name 3. Select the Dimension Name 4. Select the Property Name 5. Select a Derivation Script 6. Enable or Disable the Property Derivation 7. Input a Description 8. Select Save to save the record.

29 29 Note: All Scripts are created and managed in the Scripts Module. To Edit a Property Derivation 1. Right click on a row and select Edit Properties from the Menu to display the Edit Derivation popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

30 30 To Delete a Property Derivation 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Property Derivation. Note: Only one Property Derivation can be deleted at a time. Templates Templates are utilized in Workflows to notify Requestors, Reviewers and Approvers of the actions taken during the Request and Workflow process. The Template Grid displays all the available templates that have been created.

31 31 Template Grid Variable Tags are available to customize the templates and make them dynamic. Variable Tags: <REQUEST_ID> <REQUEST _DESCRIPTION> <REQUESTOR_FIRST_NAME> <REQUESTOR_LAST_NAME> <EPMWARE_URL> <LINE_NUM> <TASK_STATUS> <USER_NAME> To Add an Template 1. Select the icon to display the Template Properties popup box. 2. Input text and Variable Tags for all required fields. 3. Select Save to save the record.

32 32 Template Example To Edit an Template 1. Right click on a row and select Properties from the Menu to display the Template Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes. To Delete an Template 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display

33 33 3. Select OK to delete the Template. Note: Only one Template can be deleted at a time. Global Settings Select ConfigurationMiscGlobal from the navigation menu to access Global Settings. Configure Global Settings for the entire EPMware application. Select a tab to configure: Settings Application Settings Web Settings User Defined Field Settings Settings Settings contains all the Global Setting for EPMware application. The following are the available settings: Domain Name Server Name Timeout in ms From Address Maximum # of file attachments Maximum length of the Maximum size of the of the attached file Non Production environment prefix Production Database Name

34 34 Global Settings Example To Edit Settings 1. Double click on the Value or Description field to switch the field to edit mode 2. Edit the properties as required. 3. Select to save the changes.

35 35 Application Settings Application Settings contains all the Global Application Settings for the EPMware application. The following table contains all the available Application settings: Application Setting BPMA Server URL Database Trace Identifier Date Format Description BPMA Server URL Debug database Trace identifier Specify Date Display format (For example MM/DD/RRRR) Debug level Specify Debug Level (1-Error only, 2- Warning,3-All) Debug Purge Days Deployment Service Sleep Interval EPMware Application URL Essbase Home Directory Files Archive DB Directory Hyperion Cluster Name Specify # of Days to retain Debug information Deployment Service Sleep Interval (Seconds) Specify URL of the EPMWARE application Specify Essbase Home directory Specify DB directory to archive files Specify Cluster name

36 36 Hyperion Home Directory Organization Name SSH Port SSH Timeout (in minutes) Specify prefix for the Debug files Specify prefix for the Report Files Stage DB Directory Temp DB Directory Turn On/Off debug messages Turn On/Off debug messages to be inserted into debug table User Authentication Directory Type (LDAP or MSAD) Workflow Service Sleep Interval Workspace Server URL Specify directory for EPMA/HYPERION Home Specify Organization name Specify port # for SSH communications Specify SSH Timeout in minutes Specify prefix for the Debug Files Specify prefix for the Report Files Specify DB directory for temporary file generations Specify DB directory for temporary file generations Enable/disable debug messaging Enable/disable debug messaging in table User Authentication Directory Type (LDAP or MSAD) Workflow Service Sleep Interval (Seconds) Workspace Server URL

37 37 Global Application Settings Example To Edit Application Settings 1. Double click on the Value or Description field to switch the field to edit mode 2. Edit the properties as required. 3. Select to save the changes.

38 38 Web Settings Web Settings contains all the Global Web Settings for the EPMware application. To Edit Web Settings 1. Double click on the Value or Description field to switch the field to edit mode 2. Edit the properties as required. 3. Select to save the changes. User Defined Settings User Defined Settings define up to 3 custom User Defined Fields for the Request Page: UD1, UD2 and UD3. The fields can be used to capture data on the Request for items such as Request Type, Internal Ticketing Systems or other Tracking Systems. User Defined Fields

39 39 User Defined Settings Description Enabled Display Type Display Label Data Type Lookup Required On/Off Input or Lookup Description displayed on the Request String, Numeric or Date Reference to values defines in the Lookup table. On/Off Identifies if the User Defined Field is required. To Edit User Defined Settings 1. Double click on a field in the column to switch the field to edit mode 2. Edit the properties as required. 3. Select to save the changes. Lookups Select ConfigurationMiscLookups from the navigation menu. Configure items populated in dropdown boxes throughout the entire EPMware application. Select a Lookup by using Search by Name or Description or by scrolling using the arrow buttons on the upper right.

40 40 To Add a Lookup 1. Select the icon in the header to display a new header record. 2. Input the Lookup Name and Description. 3. Select Save to save the header. Note: The Lookup record must be saved before a Lookup Code can be added. Caution: Seeded Lookups are not allowed to be edited or deleted. They are Read only.

41 41 Lookup Code Settings Description Enabled Lookup Code Meaning Description Display Seq.# On/Off Code to Reference Lookup Description displayed on the Control Description of the Lookup record To order the Lookup values To Add a Lookup Code 1. Scroll to or Search for the Lookup record. 2. Select the icon to display the Add New Lookup Code popup box. 3. Input the required fields. 4. Select Save to save the record.

42 42 To Delete a Lookup Code 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Lookup Code. Note: Only one Lookup Code can be deleted at a time. To Edit a Lookup Code 1. Right click on a row and select Properties from the Menu to display the Lookup Code Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

43 43 Security The Security module is used by the Administrator for the initial configuration and for ongoing administration of Security. The Security module is comprised of the following sections: Users Groups Classes Provisioning Security Model The Security model consists of three components: Roles Requestor Reviewer Approver

44 44 Default Modules Metadata Logic Audit Security Config Workflow Deployment Security Classes - Defined by Administrator Users and Groups are provisioned for each component using Security Provisioning. Security Rules The following rules are applied in the security engine to qualify menu, content and operations that users perform in the application: Security classes are created by the Administrator to secure Applications and Dimensions. Modules dictate which menu options are available to the User. Roles dictate the functions users perform. Note: Modules and Roles are system defined and can t be edited. Roles Roles determine the functions that are performed by the user. A user must be assigned at least one Role. Requestor Users who are assigned this role create new Requests for metadata. The Requestor role does not allow Review or Approval of requests. Reviewer Users who are assigned this Role review metadata Requests. The Approve and Reject menu items for Users Actions on the Request page are displayed for this role if following conditions are met:

45 45 User has the Reviewer role. User has Metadata module assigned. User has access to Request level security constraints: o Reviewer is assigned to this task OR in the Group assigned to this task. See (Request Workflow Workflow TasksReview Task.) o Request is in Pending Review Stage. Note: When the Request is Submitted a snapshot of Users and Groups for the Workflow that is selected for the Request are bound to the Request. Therefore, Pending and Closed Requests are not impacted if the Workflow Task is changed. Caution: Reviewers can only review Request Lines to which they have Security access. Approver Users who are assigned this Role Approve metadata Requests. The Approve and Reject menu items for Users Actions on the Request page are displayed for this Role if following conditions are met: User has the Approver role User has Metadata module assigned User has access to Request level security constraints: o Reviewer is assigned to this task OR in the Group assigned to this task. See (Request Workflow Workflow TasksReview Task.) o Request is in Pending Approval Stage. Note: When the Request is Submitted a snapshot of Users and Groups for the Workflow that is selected for the Request are bound to the Request. Therefore, Pending and Closed Requests are not impacted if the Workflow Task is changed. Caution: Approvers can only approve Request Lines to which they have Security access. Default The Default role is for Users not that are not Requestors, Reviewers or Approvers. For example, this role can be assigned to a User that will only have read access or only access to Explorer.

46 46 Users The Users page is for User administration of the EPMware application. Users can be queried, added, deleted, disabled and assigned to Groups. Note: Both Native and MSAD users can be assigned to Native Groups. Note: Select the check box in the Inactive column to disable a User. Caution: The grid Right Click Menu will not show the Delete option when the LDAP radio button is checked. To Add a Native User 1. Select the icon to display the Add Native User popup box. 2. Input Required Fields 3. Select Save to add the User.

47 47 To Edit a Native User 1. Right click on a row and select Edit User from the Menu to display the Edit User popup box. 2. Edit the User profile as required. 3. Select Save to save the changes. Note: If Edit User is selected for an LDAP User, the input boxes will be grayed out.

48 48 To Delete a Native User 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the User. Note: Only one User can be deleted at a time. Caution: The Delete menu option will be grayed out if an LDAP User is selected.

49 49 To View Groups for a User 1. Right click on a row and select View Groups from the Menu to display the View Groups popup box. 2. Select Close to close the window. To Assign a Group to a User 1. Right click on a row and select Assign Groups from the Menu to display the Assign Groups shuttle window. 2. Select a Group from the available Groups in the left pane 3. Select the Right Arrow and push the Group to the right pane to assign it to the User. 4. Select Save to save the changes.

50 50 To Un-assign a Group for a User 1. Right click on a row and select Assign Groups from the Menu to display the Assign Groups shuttle window. 2. Select the Group to remove from the right pane. 3. Select the Left Arrow and push the Group to the left pane to un-assign it for the User. 4. Select Save to save the changes.

51 51 Groups The Groups page is used to Administer Groups for the EPMware application. Note: Native and LDAP users can be assigned to Native Groups. Note: Select the check box in the Inactive column to disable a Group. To Add a Group 1. Select the icon to display the Add New Group popup box. 2. Input Name and Description

52 52 3. Select Save to add the Group. To Edit a Group 1. Right click on a row and select Edit Group from the Menu to display the Edit Group popup box. 2. Edit the Properties as required. 3. Select Save to save the changes.

53 53 To Delete a Group 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Group. Note: Only one Group can be deleted at a time. To View Users for a Group 1. Right click on a row and select View Users from the Menu to display the View Users popup box. 2. Select Close to close the window.

54 54 To Assign a User to a Group 1. Right click on a row and select Assign Users from the Menu to display the Assign Users shuttle window. 2. Select a User from the available Users in the left pane 3. Select the Right Arrow and push the User to the right pane to assign it to the Group. 4. Select Save to save the changes. To Un-assign a User from a Group 1. Right click on a row and select Assign Users from the Menu to display the Assign Users shuttle window. 2. Select the User to remove from the right pane. 3. Select the Left Arrow and push the User to the left pane to un-assign it for the Group. 4. Select Save to save the changes.

55 55 Security Classes Security Classes are used to secure Applications and Dimensions in EPMware. Security Classes are created by the Administrator and are assigned to applications and dimensions. Security Classes are Provisioned on the ConfigurationSecurityProvisioning page. Provisioning assigns the Security Class to a Security Group and assigns Read or Write access.

56 56 To Add a Security Class 1. Select the icon to display the Add Server popup box. 2. Input the Security Class Name and Description (Optional) 3. Select Save to add the Security Class. To Edit a Security Class 1. Right click on a row and select Properties from the Menu to display the Class Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

57 57 To Inactivate a Security Class 1. Select the Inactivate check box on the row in the grid. 2. Select to save the changes. To Delete a Security Class 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Security Class. Note: Only one Security Class can be deleted at a time.

58 Security Provisioning Security Provisioning is used to assign access to Groups in the EPMware application. It is a four tiered Security model consisting of Groups, Roles, Modules and Classes. At least one selection from each tier is required to properly provision a Group. The Security Provisioning grid will display the following three sections in the columns: Roles, Modules and Classes. The rows of the grid display the Groups created in Security Groups. Each intersection of the rows and columns has a checkbox or dropdown to define the group s access rights. The Roles Section has User Roles for EPMware, Requestor, Reviewer, Approver and Default. The Modules Section controls access to the EPMware Modules. The Workflow and Deployment columns of the Modules Section have a dropdown to select Read, Write or None access. The Classes section displays all the Security Classes created in EPMware. Each Security Class and Group intersection has a dropdown to assign Read, Write or None access. 58 Group Search Page Navigator Note: See Security Groups, Security Roles and Security Classes for more information on creating and administering Groups, Roles and Classes. Caution: The Navigation Menu will not display Modules for Users of a Group if the Group is not assigned access to that Module.

59 59 Modules Modules control access to the following EPMware elements: Metadata - Grants access to Metadata Requests Scripts - Grants access to Script Requests Audit - Grants access to the Audit Module Security - Grants access to Security Configuration Config - Grants access to EPMware Configuration Workflow - Grants access to the Workflow Module Deployment - Grants access to the Deployment Module To Provision or Edit a Group 1. Use the Group Search Box or the Page Navigator to display the Group. 2. Select at least one checkbox or dropdown value from the Roles, Modules and Classes sections. 3. Select to save the Provisioning changes. Workflow The Workflow module is used by the Administrator for the initial configuration and the ongoing maintenance of EPMware Workflows. The Workflow module is comprised of the following components: Workflow Tasks Workflow Builder A Workflow is comprised of a series of user defined Stages which contain Workflow Task. Workflow Tasks are created and maintained at WorkflowTasks. Workflows are created at WorkflowBuilder.

60 Workflow Tasks Tasks are individual operations which are then assigned to Stages. Tasks are associated with an Template, Security Group and Custom Function. 60 A Task consists of the following components: Name - User defined name for the Task Description - A Description of the Task Action: o Review o Approve o Validate o Deploy o Notify o Custom Template - Templates created using Template Configuration Security Group - Groups created using Group Configuration. (Only valid for Review and Approve Actions). Custom Function - A script defined in the Logic Bulder # of Approvals Defines how many Approvals are required for the Task. (Only valid for Review and Approve Actions). To Create a Workflow Task 1. Select the icon to display the Task Properties popup box. 2. Input the Task Name and Description (Optional) 3. Select an Action from the dropdown box.

61 61 4. Select an Template from the dropdown box. 5. Select a Security Group from the dropdown box 6. Input the # of Approvals. 7. Select Custom Function (only applicable if Action is Custom) 8. Select Save to save the Task. To Edit a WorkFlow Task 1. Right click on a row and select Edit Properties from the Menu to display the Task Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

62 62 To Delete a Workflow Task 1. Right click on a row and select Delete Task from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Workflow Task. Note: Only one Workflow Task can be deleted at a time.

63 63 Workflow Builder Workflows are created and configured by adding Stages to a Workflow. Stages are comprised of a set of Tasks. Tasks are individual operations defined by the Administrator using WorkflowTasks. The Tasks are then assigned to a Stage. Note: Changing a Workflow will not affect Requests in progress. A snapshot of the workflow is taken when the Request is created and is bound to the Request, so the request will continue to use the workflow as it existed at the time the Request was created. Click on the green Start node to view the Workflow properties or click on a Stage node to view the Stage properties in the Grid. Workflow Properties: Name - User defined name Priority - Assigns a Priority to the Workflow Description - User defined description Security Class: Assigns a Security Class to the Workflow Enabled - Enable or Disable the Workflow Visible - Makes the Workflow visible in the drop down on the Request Metadata - Workflow is valid for Metadata Request Scripts - Workflow is valid for a Script Request To Create a Workflow 1. Select the icon to display the Workflow Properties popup box.

64 64 2. Input the Workflow Name and Description (Optional) 3. Select a Priority from the dropdown box. 4. Select an Template from the dropdown box. 5. Select a Security Class from the dropdown box. 6. Select the Enabled, Visible, Metadata and Scripts checkboxes as required. 7. Select Save to save the Task. To Edit a Workflow 1. Right click on the green Start node and select Edit Properties from the Menu to display the Workflow Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

65 65 To Delete a Workflow 1. Select the Workflow to delete from the Workflow drop down 2. Click on the Actions button and select Delete Workflow from the Menu. 3. The following confirmation popup will display 4. Select OK to delete the Workflow.

66 66 Workflow Stages Any combination of Workflow Stages can be added to a Workflow to meet company requirements. Workflows are created and configured by adding Stages to a Workflow. Stages are comprised of a set of Tasks. Tasks are individual operations defined by the Administrator using WorkflowTasks. The Tasks are then assigned to a Stage. Workflow Stage Properties: Stage # - Determines where the Stage is positioned in the workflow. Name User defined name Description - User defined description Action: o Review o Approve o Validate o Deploy o Notify o Custom To Add a Stage to a Workflow 1. Select the Workflow from the Workflow drop down 2. Click on the Actions button and select Create Stage from the Menu to display the Stage Properties popup box. 3. Input a number for Stage # to define the order of the Stage in the Workflow. 4. Input the Stage Name and Description (Optional) 5. Select an Action for the Stage. 6. Select Save to add the Stage.

67 67 Note: The Stage # determines where the Stage is positioned in the workflow. For example Stage# 20 will appear after Stage# 10 etc. To Assign a Task to a Stage 1. Select a Stage node to display the Stage Configuration Grid 2. Click on the Actions button and select Assign Task from the menu to display the Assign Tasks popup box. 3. Select the checkbox next to the Tasks to assign it to the Stage. 4. Select Save to assign the Task.

68 68 To Edit Task Properties from Workflow Builder 1. Select a Stage node to display the Stage Configuration Grid 2. Right click on a row and select Edit Properties from the Menu to display the Task Properties popup box. 3. Edit the properties as required. 4. Select Save to save the changes.

69 69 Deployment The Deployment module is used by the Administrator for the initial configuration and the ongoing maintenance of EPMware Deployments to the target applications. The Deployment module is comprised of the following Components: Deployment Manager Deployment Monitor Deployment Schedule Deployments are created by Application, Workflow or Request. Pre-Deployment and Post-Deployment scripts may be added to customize the Deployment process.

70 70 Deployment Manager Deployments are created and managed with Deployment Manager. A Deployment consists of the following components: Name - User defined name for the Task Description - A Description of the Task Type: o Application - Will deploy all approved Request the application o Workflow - Will deploy all Approved Requests for the Workflow o Request - Deploys and individual or group of Requests. Pre-Deployment Scripts - A script created in Logic Builder which will run a Pre- Deployment process before the metadata is deployed to the target application. Post-Deployment Scripts - A script created in Logic Builder which will run a Post-Deployment process after the metadata is deployed to the target application. Note: All scripts are created and managed in Logic Builder. To Create a Deployment 1. Select the icon to display the Add Deployment popup box. 2. Input the Deployment Name and Description (Optional) 3. Select a Deployment Type. 4. Select a Pre-Deployment Script.

71 71 5. Select a Post-Deployment Script. 6. Select Save to save the Deployment To Edit a Deployment 1. Right click on a row and select Edit Properties from the Menu to display the Deployment Properties popup box. 2. Edit the properties as required. 3. Select Save to save the changes.

72 72 To Delete a Deployment 1. Right click on a row and select Delete Task from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Workflow Task. Note: Only one Deployment can be deleted at a time. To Schedule a Deployment 1. Select the icon to display the Schedule Deployment popup box. 2. Select the frequency for the Deployment Schedule 3. Input or Select the parameters for the Schedule.

73 73 4. Select Save to save the Deployment Schedule. Deployment Monitor The grid will display each Deployment instance that is generated based on the Deployments defined on the Deployment Manager tab. To redeploy a deployment that has a status of Failed or Partial in the Status column, right click on the row and select Redeploy. This will place all un-deployed requests back in the pool for the next scheduled deployment. To redeploy an individual Request, click on the Deployment ID to display the Deployment Status popup then right click on a row and select Redeploy. The redeployment for the individual Request will run on the next scheduled Deployment.

74 74 Monitor Grid Deployment Id - Unique ID assigned to the Deployment. Name - Name of Deployment as defined on Manager Tab. Description - Deployment description as defined on Manager Tab. Type - Deployment Type defined on the Manager Tab Application Workflow Request Start Time - The date and time that the Deployment instance began running. End Time - The date and time that the Deployment instance completed. Status - Will display either Running or Completed Log - Will display the log file pertaining to this deployment instance. Grid Filter The Filter icon will display the Grid Filter popup Filter Icon

75 75 Deployment Status Note: The Deployment Status popup is displayed by clicking on the Request ID in the Deployment Monitor Grid

76 76 Status Legend Completed -This icon indicates the deployment has completed successfully. Pending - This icon indicates the deployment has an action pending, but the deployment will finish once the pending action is complete. Partial - A partial status is indicated when some metadata Request lines on a Request have been deployed, but other lines have failed to deploy. To change from Partial status to Complete, the failed line on the Request must be fixed and the Deployment Redeployed or the Deployment must be manually Closed. Failed - This icon will indicate the deployment has failed and will not finish without user intervention. Running -This icon will indicate the deployment does not have any actions pending, and is currently running. Note: Right clicking on a row in the Deployment Status popup will display the menu option Redeploy. Selecting Redeploy will put the individual Request in the eligible pool for the deployment engine to pick up on the next run. Deployment Schedule The grid displays all scheduled Deployments to target applications. It is used to monitor future Deployments. Future Deployments can be changed on the Manager Tab by modifying the Deployment's schedule. Grid Columns: Name Description Next Deployment Date Frequency Type

77 77 Logic Builder Logic Builder is used to create, delete, edit and validate scripts for use in other EPMware Modules. A Logic Builder grid displays all the scripts. Left clicking on a row will display the script in the pane below the grid. The script can then be validated, edited and saved. If delete is selected, a popup will display to confirm deletion of the Script. A referential integrity check is performed to ensure the script has not been assigned anywhere in the application. If the script is being used, an error message displays notifying the user to disassociate the script and then attempt to delete it again. Clicking the icon in the editor pane will validate the script.

78 78 Note: Use the checkbox on the row to Enable or Disable a script. A script will not appear in any modules if disabled. To Create a Script 1. Select the icon to display the Create Script popup box. 2. Input the Script Name and Description (Optional) 3. Select a Script Type. 4. Input DB Function Name if applicable. 5. Select the Enabled checkbox to enable a script or uncheck to disable. 6. Select Save to save the script.

79 79 To Upload a Script File 1. Select the icon on a row in the grid. 2. Use the Browse button to select the script file. 3. Select the Upload button to upload the file or Cancel to cancel the upload. Note: A script file can only be uploaded to an existing Script. To Edit a Script s Properties 1. Right click on a row and select Properties from the Menu to display the Edit Script popup box.

80 80 2. Edit the properties as required. 3. Select Save to save the changes. To Delete a Script 1. Right click on a row and select Delete from the Menu. 2. The following confirmation popup will display 3. Select OK to delete the Script.

81 81 Logic Builder Editor The Logic Builder Editor is displayed when a script is selected in the grid by left clicking on the row. The script is displayed in the Editor at the bottom of the page. The name of the script is displayed in the blue box. Select the Save icon to save the changes. To Edit a Script 1. Left click on the script in the grid to display it in the Logic Builder Editor. 2. Edit the script as required 3. Select the icon to validate the script. 4. Select the icon to save the changes. Services The Services page is located at AdministrationServices and has the current status of the EPMware Services. The Workflow and Deployment services can be Stopped and Started from this page.

82 82 ERP Import The ERP Import module is used by the Administrator to import metadata from an ERP source system into EPMware. This module also has an ERP Import Scheduler to schedule imports. The ERP Import module is comprised of the following components: ERP Import Builder ERP Import Mapping ERP Import Monitor ERP Import Builder ERP Imports are created and managed with the ERP Import Builder. An EPMware interface table is populated with data from the source ERP system via a SQL query.(see Appendix A for the Interface table technical details.) The data in the EPMware interface table is then mapped to the metadata Request attributes for the EPMware application. The Request Header and the Request Line Items are then populated with the data from the ERP Import and the Request is now ready for Review and Approval.

83 83 An ERP Import consists of the following components: Interface Name - User defined name for the interface Description User defined description Application - Target Application Dimension - Target Dimension Workflow Priority - Workflow Priority as deinfed in the Workflow module Workflow - Workflow as defined in the Workflow module Partial Allowed - Select if Partial Load is allowed Enabled - Enable the ERP Import Launch Workflow - Select if Workflow should launch after import Interface Table Name - Define interface table name. Pre-Execution - Run script before import Post-Execution - Run script after import Template (Success) Template (On Error) To Create an ERP Import 1. Select the icon to display the Create ERP Import popup box. 2. Input the Interface Name and Description (Optional) 3. Select an Application 4. Select a Dimension 5. Select a Workflow Priority 6. Select a Workflow 7. Select the Partial Allowed checkbox if partial loads are allowed.