Obligation form

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 3 Minuten Lesedauer

    • The obligation form provides the details to create or modify an obligation record in Obligation Management.

    Tabelle : 1. Obligation record form
    Field Description
    Number An auto-generated unique number for the obligation record.
    Contract Unique number of the contract repository record.
    Name Name of the obligation.
    Category Category of the obligation. The available values are:
    • Operational or service delivery
    • Legal
    • Commercial
    • Compliance
    • Governance
    Subcategory Subcategory of the obligation.

    The available values depend on the selected category.
    Active Option to activate the obligation.

    If a recurring schedule has been defined for obligation tasks, activating the obligation creates obligation tasks based on the defined schedule.
    Approver group Group whose members have appropriate permissions to approve or reject an obligation task.
    Approver Member of the approver group assigned to approve the obligation tasks.
    Task assigned to User to whom the obligation tasks will be assigned by default. This value can be overridden by assigning a user once the obligation task is created. A notification email is sent to the assigned user.
    Start date Date from which the obligation will be in effect.
    End date Date on which the obligation ends.
    Instructions Actions that must be performed as part of the obligation.
    Description Extract from the contract that describes the obligation.
    Schedule type Schedule type of the obligation tasks.
    Adhoc
    Obligation must be fulfilled once or at irregular intervals. You must create obligation tasks manually.
    Recurring
    Obligation must be fulfilled regularly at a defined interval. Obligation tasks are automatically created based on the interval specified in the Repeats field and according to the value in the Task creation lead time (days) field.
    Repeats

    This field appears only when Recurring is selected from the Schedule field.

    Hinweis:
    For monthly or yearly repeats, the first obligation task is due on the selected date and recurring obligation tasks are due on the same day of the month or year as the initial value. For example, if you select 2024-08-10 as the Due date value, the first obligation task will be due on the 10th of August 2024 and the subsequent tasks will be due on the 10th day of the month in the specified interval or on that date every year. If you select the 31st day of a month as the Due date value, the obligation tasks for months with less than 31 days will be due on the last day of that month.
    The available values are:
    • Daily - Obligation tasks are created daily and are due every day between the start date and end date of the obligation record.
    • Weekly - Obligation tasks are created every week. The value in the Repeats field that appears when this value is selected determines the days of the week when the obligation tasks should be fulfilled.
    • Monthly - Obligation tasks are created once a month and are due on the day of the month specified in the Due date field that appears when this value is selected.
    • Every three months - Obligation tasks are created every three months and are due on the day of the month specified in the Due date field that appears when this value is selected.
    • Every six months - Obligation tasks are created once a month and are due on the day of the month specified in the Due date field that appears when this value is selected.
    • Yearly - Obligation tasks are created once a year, with the first obligation task being due on the selected date and recurring obligation tasks due on the same date every year.
    Task creation lead time (days) This field appears only when Recurring is selected from the Schedule field. It determines the number of days before the task’s due date when the obligation tasks should be automatically created.