Create new diagram template

You can create new diagram templates under Reports or Analyses > Diagram Templates.

Description of input fields

• Name: For recognizing it in the list of automatic exports
• Language of title: Displayed as a selectable title when the dashboard is used in the special Search screen for diagrams|search screen for diagrams. The language can be changed and must be entered separately in all the languages required.
• Description: Explains the control parameters and contents that are fetched; ideally, als explains what the diagram can be called.
• Parameter 1- n: Up to 20 parameters can be passed which are replaced in the SQL. This option is often used to control the display language of the diagram or to optimize the content to the diagram viewer in accessing the entities being examined. (E.g. My employees only)
• Test variables: Used to put the export through a test run when creating it. Enter the parameters in the same way that you then want them to be replaced in the test run. (e.g.: UrlID1=123, UrlID2=456)
• SQL statement: An in-depth knowledge of the data structure in the background is required here. The parameters that are passed are used as placeholders here (e.g. Select ... from ... where Table.ColumnA = [UrlID1] and Table.ColumnB = [UrlID2] )
• Position: Specifies the order of the diagrams in the Search screen for diagrams|search screen for diagrams.
• XSLT file: The output of the result of the SQL matches a particular XML structure. The XSLT is now suitable for adjusting the standard XML output to the Flash player of www.maani.us.
• Current XSLT: and current SQL statement: If it is a standard Umantis diagram, we regularly provide updates here. Save the new XSLT and add it instead of your XSLT file. The same applies to the SQL... However, here there is no need to temporarily save it to your desktop.
• Set type and authorization for dynamic diagram screen:
  • Diagram type: This setting controls the display on the search diagram screen. With it, you can group your diagram by subject, from which one dynamic diagram screen is generated respectively.
    • Type "Employee (positions)" bundles diagrams about employees that can be called up from "/DashboardSearchScreen1"
    • Type "Employee review meetings (positions)" bundles diagrams about employee review meetings that can be called up from "/DashboardSearchScreen2"
    • Type "Persons (Persons)" bundles diagrams about persons that can be called up from "/DashboardSearchScreen3"
    • Type "Events (Courses)" bundles diagrams about events that can be called up from "/DashboardSearchScreen4"
  • Position: Defines the order within a diagram type.
  • Displayed table:There are three tables on each dynamic diagram screen. Here, you decide which of the three tables should appear along with the diagram. Depending on the subject, different content can be shown in each table. Use the view configuration mode as a tool. Some of the three tables also have different filters, such as, for example, active employee, past employee, which are noted in the original title of each table.
    • Employees (Positions):
      • Table 1: Employee positions of only current employees
      • Table 2: Employee positions of only current employees (identical to Table 1)
      • Table 3: Employee positions of current and past employees
    • Employee review meetings (Positions):
      • Table 1: Employee positions of only current employees with employee review meeting
      • Table 2: Employee positions of current and past employees with employee review meeting
      • Table 3: Employee positions of current and past employees even without employee review meeting
    • Persons (Persons):
      • Table 1: Employee
      • Table 2: External persons
      • Table 3: All persons
    • Events (courses):
      • Table 1: current and historic events
      • Table 2: current and historic events (identical to Table 1)
      • Table 3: only current events
  • Visible for module owner:Defines which module owner can view this diagram. If nothing is selected, the content is visible for all module owners.
  • Visible for role: User roles, for which this diagram is visible. If nothing is selected, the content is visible for all user roles.
• Set search: Here you can define which search criteria should be available for each diagram.

Snippets

• For additional security in EM, you should insert the ACR permissions with [--AccessRights--] into the SQL before the WHERE condition.
• Snippet for searching from overviews: E.g. Analyze Time-To-Hire graphically in the jobs overview in AM [StartSearchIDs "Pos"."Pos+id" in (SearchIDs) EndSearchIDs]
• Should be used in AM to restrict access to your own branch offices [StartRestricted and "PersPos"."BranchID" IN ([AllBranchIDs]) EndRestricted],
• Sample search snippet in the search screen for diagrams: [START_OrgUMSL and "Pos"."OrgDat+OrgUnit" IN ( (Search_OrgUMSL) ) OrgUMSL_END]
• Another sample search snippet in the search screen for diagrams: [START_Jobfamilie and "Pos"."RqOther+JobDescription2" Like '(Search_Jobfamilie)' Jobfamilie_END]

In general it is the case that a snipped must be added in such a way that the SQL can run both "with" and "without" this bit. Where necessary, snippets are parsed before running the SQL, or cut out completely.

Excel export in the dashboard search screen

No variables are supported in the export SQL. Only the following block is required as a WHERE condition:

where [StartSearchIDs "Pos"."Pos+id" in (SearchIDs) EndSearchIDs]

Here, "Pos"."Pos+id" may have to be replaced by another ID column.

Actions

• Test view: ...Your test variables will now be used. The link in the actions automatically puts together the test call so that you will get the diagram in response.
• Show SQL result: Here you can test the first step in the configuration, the SQL. The test parameters are required here as well.
• Delete: Deletes the entire diagram configuration.