Configuring a Mixin type for Capturing Document Revisions - Configuring a Mixin type for Capturing Document Revisions - This section describes how system administrators can configure a Mixin type SysVersionable and add it to a Content Type. - Content Innovation Cloud - Hyland for Workday - Current/Hyland-for-Workday/vne1753949166852 - Current - Current

Hyland for Workday

Platform
Content Innovation Cloud
Product
Hyland for Workday
Release
Current
License
ft:lastPublication
2026-10-12T22:09:45.336544
ft:locale
en-US

This section describes how system administrators can configure a Mixin type SysVersionable and add it to a Content Type.

Before you create revisions of one or more documents captured using Hyland for Workday, you must add the Mixin type SysVersionable to a Content Type using Studio Modeler. Default Content Types that are installed automatically during provisioning support revisions.
Note:
  • Complete the instructions in this section only if you are using the Hyland Content Innovation Cloud (CIC) content repository.

  • For more information on Mixin types, see the Mixins chapter in the Hyland Automate Modeler documentation.

To add the SysVersionable Mixin type to a Content Type:

  1. Sign in to the Modeling Application and open the Workday project.
  2. Select how to create the content type:
    • Click Create > Content Type.
    • Click the three dots next to the Content Types drop-down menu in the left-hand pane, and then select Create.

    You can also upload a JSON file with the content type. For more information on how to upload a JSON file with a content type, see the Uploading Project Elements chapter in the Hyland Automate Modeler documentation.

    The Create Content Type window is displayed.

  3. Enter the newly created content type name in the Content Type name field.
  4. Add an optional description in the Content Type description field.
  5. From the drop-down Parent Content Type field, select the parent content type. The parent content type properties will be inherited by the new content type. The default selection is None, which means that no content type properties will be inherited by the newly created content type.

    The default content types that come built-in with the Studio Modeler application are under the Default Content Types section.

    Any custom-made content type can be selected under the Custom Content Types section.

    Note:

    If you select None as the Parent Content Type, you need to add a Schema or a Mixin to it later.

  6. Click Create Content Type.
    The created content type is opened in the application as a new tab.
  7. In the Schemas section, use the + icon to add schemas to your content type. If you used a parent content type that already had schemas assigned, they are listed as Inherited schemas in this section.

    If you want to remove an already added schema, use the - icon on the right.

    Note:

    You cannot remove the inherited schemas. For more information on schemas, see the Creating and Configuring Schemas chapter in the Hyland Automate Modeler documentation.

  8. In the Mixins section, use the + icon to add the SysVersionable mixin to your content type. If you used a parent content type that already had mixins assigned, they are listed as Inherited mixins in this section.

    If you want to remove an already added mixin, use the - icon on the right.

    Note: You cannot remove inherited mixins.
  9. Once editing is done, use the Save Content Type cloud icon at the top bar to save the created content type.
    A blue window reading Content Type saved is displayed at the bottom.

    The new content type is created and saved.

  10. Save the new app, validate it, and then click Release.
    Note: For more information on how to validate and release an app, see the Validating Projects and Releasing Projects chapters in the Hyland Automate Modeler documentation.
  11. Sign in to the Hyland Automate Administration application to upgrade the project.
    Note: For more information on how to upgrade a project, see the Upgrading chapter in the Hyland Automate Administration documentation.