Create an Event

Learn how to create and configure an event.

Create an event

Events happen at a specific moment in time to a specific individual. In Visier, events happen to subjects. For guidelines about whether an event is the right object type to create, see Should I create an event?

Who can use this feature?

Users with this profile:

  • Advanced Model Developer

Not sure if you have this feature or capability? Reach out to your administrator.

  1. In a project, on the navigation bar, click Model > Analytic Objects.
  2. Click Create Analytic Object.
  3. In Analytic object type, select Event.
  4. Type a display name and description.
  5. When finished, click Create.

Configure an event

Configure an event by creating properties, defining the list of properties displayed in the Detailed View visual, changing the event's settings, and more.

Note:  

  • Settings and References are only available with the Advanced Model Developer profile.
  • Suggested Key Groups is only available with the Analytic Model Developer profile or Advanced Model Developer profile.
  1. In a project, on the navigation bar, click Model > Analytic Objects.
  2. Select an event.
  3. In Attributes, create attributes to hold specific data for the object. For more information, see Properties, Dimensions, and Concepts.
  4. In Settings, define the object's settings. For more information, see Event settings below.
  5. Optional: Do any of the following configurations:

Example: Employee Exit

Let's say you want to configure a new event called Employee Exit. This event represents employee exits from your organization. To set up Employee Exit, you would make the following configurations:

  • Attributes: Create attributes that are essential for analysis, such as Employee Exit Model, Employee Exit Reason, Employee Exit Type, Other Involuntary, Other Voluntary, Reduction in Force, Resignation, Retirement, Termination, and System Termination.
  • Settings: Configure the following settings.
    • Tags: Retention. This identifies Employee Exit as part of the Retention content category.
    • Captions: Occurrence Captions = Not set. This means that exit events will inherit the captions of Employee Exit's associated subject, Employee. Employee's captions are Full Name and Job Name, meaning the Employee Exit will display Full Name and Job Name in Detailed View.
    • Subject: Employee. This means that Employee Exit is associated with the Employee subject.
    • Ending event: Enabled. This defines Employee Exit as an event that causes a member's record to become non-active.
    • Default metric: Not set. This isn't required for events.
    • Data category: Tenant. This means that Employee Exit data is loaded through the Tenant data category. For more information, see Data Categories.
    • End date: Disabled. This means that Employee Exit inherits Employee's data end date. In this scenario, Employee's end date is inherited from the data version settings, so Employee Exit also inherits the data version settings.
  • References: No configuration required.
  • Suggested Key Groups: Add key groups to suggest to users, such as High Performer, Manager, and Critical Employees. These key groups will be suggested as group bys when users interact with exit data in visualizations.
  • View Details: Add properties that you want to appear in the Detailed View visual, such as Employee, Employee ID, Employee Exit Reason, Employee > Tenure, Employee > Job Name, Employee > Gender, Employee > Manager Status, and Employee > Performance Rating. These properties will be visible to users in Detailed View.
  • Basic Information: If Description is blank, add "An event that records the termination of an employee.".

Event settings

The event settings allow you to modify its default metric, associated subject, and more.

Who can use this feature?

Users with this profile:

  • Advanced Model Developer

Not sure if you have this feature or capability? Reach out to your administrator.

Tags

Tags are user-defined categories that group content in the solution. A tag can apply to multiple object types, including analytic objects, metrics, and guidebooks. A user may filter for objects with a particular tag throughout the solution. For this setting, add tags to identify the object as part of a specific content category. For more information about tags, see Create and Assign Tags to Content.

Example:  

The Compensation tag is used for the Pay Change Events metric, the Total Cost of Workforce concept, the Compensation Type dimension, and the Compensation Payout event. This tag therefore groups these objects together as relating to compensation. The Compensation tag itself is allocated to the Talent module, meaning it exists within that solution.

Captions

Captions help the user identify a subject member or event occurrence. Use an instance caption to label members or occurrences by their property values; use a secondary caption for additional identification.

If a caption is set, it:

  • Displays the property in the Detailed View visual. For example, if Employee's caption is Full Name and secondary caption is Job Name, Detailed View will display Jane Smith, HR Specialist.
  • Makes the subject available in the Compare room.

Example:  

The property Full Name identifies specific employees. However, this may be an insufficient caption as employees sometimes have the same name, like John Smith. A secondary caption, such as Role or Location, further identifies particular employees.

Subject

Subjects are entities, or separate and independent things, that evolve over time. They have attributes and changes to those attributes are captured over time. For this setting, select the subject that the event is associated with.

Example:  

The event Pay Change Events is an occurrence of an employee's change in pay. For this event, the associated subject is Employee.

Ending event

An ending event is the event that ends the validity interval of a subject. If enabled, this event causes the record to become NonActive; for example, Employee Exit is an ending event.

Default metric

The default metric associated with an analytic object is used to generate system alerts and prevent an empty state for charts when your users switch between dimensions that have no relationship to the metric.

If enabled on a subject, default metric allows you to view the subject's history in Detailed View.

After onboarding data, the default metric is an easy way to quickly verify that the data for an object was loaded as intended. For this setting, select a metric that will act as the default metric for the object in visualizations and will be available as a data overview in the studio experience dashboard.

Example:  

The Employee subject's default metric is Headcount. Because Headcount is a default metric for Employee, the system generates an alert for Headcount to ensure its values remain consistent and expected. When new employee data is loaded, the Headcount metric can be viewed in the dashboard as a quick way to discern if the data is accurate.

Data category

A data category represents a dataset loaded into Visier that runs on a unique data load frequency. For this setting, select the data category that you want to this analytic object and its data to be loaded in. In your tenant, you may see the following system-generated data categories:

  • Tenant: This data category is the default primary data category.
  • Usage: This data category processes Visier usage information.

Additionally, any data categories created by you or your Visier team are available to assign to the analytic object. For more information, see Data Categories.

End date

If enabled, the event's end date corresponds with the event table's metadata. If disabled, the event's end date is inherited from its associated subject.

Example: Let's say you have future-dated exits and you want to also analyze these exits differently than your subject. You can enable end date on the event to use the event's end date instead of inheriting the subject's end date.