Documentation
Documentation
Payment Reminder Flow Level
Close
Payment Reminder Flow Level
States
  • Create
    The create state indicates that the Payment Reminder Flow Level is in creation.
  • Active
    The active state indicates that the Payment Reminder Flow Level is active and may be used.
  • Inactive
    The inactive state indicates that the Payment Reminder Flow Level is inactive and may not be used.
  • Deleting
    The deleting state indicates that the Payment Reminder Flow Level is in the process to be deleted.
  • Deleted
    The deleted state marks the entity for purging from the database.
Properties
  • Configuration Name
    The payment reminder flow level configuration name is used internally to identify the payment reminder flow level configuration. For example the name is used within search fields and hence it should be distinct and descriptive.
  • Duration
    The duration defines how long the level will endure.
  • ID
    A unique identifier for the object.
  • Linked Space ID
    The ID of the space this object belongs to.
  • Payment Reminder Flow
    The flow defines the reminder flow to which the level belongs to.
  • Planned Purge Date
    The date and time when the object is planned to be permanently removed. If the value is empty, the object will not be removed.
  • Priority
    The priority indicates the sort order of the level configurations. A low value indicates that the level configuration is executed before any level with a higher value. Any change to this value affects future level configuration selections.
  • Start Time Of Day
    This value defines on which time of the day this flow level will really start. It allows to target the level for a specific time during the day.
  • Start Time Zone
    This value defines the time zone that will be used when applying the start time of day.
  • State
    The object's current state.
  • Type
    The type determines how the reminder is delivered to the customer. Once the type is defined it cannot be changed anymore.
  • Version
    The version is used for optimistic locking and incremented whenever the object is updated.