Skip to end of banner
Go to start of banner

Using Take Subscriptions out of Resting Run Definitions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Back to Subscription Main Page

APPLICABLE UP TO CRM.COM R10 - The process is available for releases up to CRM.COM R10.
For a description of the Deactivation Process for releases after CRM.COM R10 visit Using Deactivate Normal Subscriptions Run Definitions (for Normal Subscriptions) and Using Deactivate Prepaid Subscription Run Definitions (for Prepaid Subscriptions)

Table of Contents

Navigating to Take Subscription Out of Resting Definitions

BILLING > SUBSCRIPTIONS > TAKE SUBSCRIPTIONS OUT OF RESTING

What are Take Subscription Out of Resting Definitions?

Take Subscription Out of Resting Definitions, are used to define the rules to be followed when a Subscription which is still in Resting, should be disconnected once coming out of Resting instead of activated based on the Activation Conditions set in the active Billing Term Definition

The run must be executed before the Resting End date has been reached, because, if a Subscription with unsettled balance, comes out of resting and becomes Effective,before the process is executed, then it will only be disconnected once the deactivation run is executed.

To handle cases weretheabove scenario happened, you have the option to define the number of days (Resting end X days ago) the System should go back and retrieve Subscription that their Resting had ended; (the System will find any Subscription between current date and the calculated date and will check for any Subscription that came out of Resting within those days) 

Note: The disconnection will be applied at the date of execution and not the date that it came out of Resting.

Note: If you do not set the above criterion the System will retrieve Subscription whose Resting ends the day that the process is executed

Run Definitions, must be submitted once created and will be executed once or on a recurring basis, based on the defined scheduling settings. Once a Definition is executed, a Process Run is logged and once the Run is completed, the log information will be available in the respective section
The user has the option to delete the specific run as long as it is not yet executed (still in 'Draft' state).
For a Definition to be submitted it needs to have an 'Effective' Life Cycle State. The Life Cycle State can be changed between 'Effective' and 'Not Effective' using the dedicated action.

  • Navigate to Take Subscription Out of Resting Definitions and explore existing records via the Summary page. 

  • Click on the link (name or number) of the record of your interest to access the Data Entry page and see more detail, or submit the Definition. 

  • Use the Actions Menu to create a NEW Definition, modify (EDIT), or DELETE an existing one.  

  • Use BACK to return to the Summary page and CANCEL to revert any unwanted changes made to the Definition.

Check the Validations & Restrictions Table below for a list of available Actions when working with Take Subscription Out of Resting, including each Action's related validations, restrictions, and a description of its System process.  View the Attributes Table for a comprehensive description of the Take Subscription Out of Resting fields.

Take Subscriptions out of Resting Runs

Validations & Restrictions

ActionValidationsRestrictionsAdditional InformationSystem Processing
Create
  • Mandatory Fields must be defined
  • Name and alternative code must be unique
  • INPUT SETTINGS:
    • Subscription Action Type
    • Subscription Sub-Action Type must be selected
  • Resting Period only takes Integer values
  •  Not Applicable
  •  Not Applicable
Edit
  • Mandatory Fields must be defined
  • Name and alternative code must be unique
  • INPUT SETTINGS:
    • Subscription Action Type
    • Subscription Sub-Action Type must be selected
  • Resting Period only takes Integer values
  • If there is at least one scheduled Run using the same Definition, then a new Run Definition instance is created.  The new Definition will have the same values and Unified Code as the first one, an augmented version number and all the modified information.
  •  Not Applicable
Delete
  • Not Applicable
  • Run Definitions cannot be deleted if there exists at least one scheduled or completed run for that Definition
  • Not Applicable
  •  Not Applicable
Submit
  • Not Applicable
  • Subscription to be considered by the run are:
    • Subscription in Resting Life Cycle State
    • Having Resting End date equal or past the date, that the batch process is performed, and no applied resting end action
    • Any additional criteria defined in the batch process
  • Not Applicable
  • Deactivate Subscription actions will be applied to the Subscription that should be disconnected on coming out of their Resting Period

 

Attributes

An * indicates a field is mandatory 

NameDescription
Main Information
Name*The name of the process run definition
Alternative code*The alternative code of the process run definition. Unless otherwise specified, the Alternative Codes for new entries default to the Name initials in capital letters.
DescriptionA description of the process run definition
Life cycle state

The Life Cycle State of the process run definition which can be

  • Effective
  • Not effective

Only effective process run definitions can be used

Unified CodeAnautogeneratedcodewhich is used to group the various instances of the process run definitions
Version

An auto-generated number which is used to specify the version of each Run Definition. If the version number is already in use by a Run, a new Run Definition version is created each time the Definition is edited. 

The VIEW PREVIOUS VERSIONS link allows you to search and view previous versions of the Definition.

Scheduled DateA Read-only field which is available once a Run is scheduled and designates the latest date that the Run was executed or is scheduled to be executed on.
Input Settings
Subscription Action TypeThe action type that will be used to classify each  Deactivate Subscription action that will be applied
SubscriptionSub ActionTypeThe action type that will be used to classify each  Deactivate Subscription action that will be applied
Criteria
Subscription Criteria
Subscription TypesA selection of Subscription Types. Only Subscription of that type will be retrieved for processing
Price PlansA selection of Price Plan. Only Subscription having effective billing terms with one of the selected Price Plan will be retrieved for processing. If no Price Plans are specified then all Price Plans are considered as applicable
Binding StateA selection ofBindingStateswhichincludes three options, any, in binding and out of binding. Only Subscription having effective billing terms with Binding States equal to the selected stated will be retrieved for processing
Binding PeriodsA selection of Binding Periods. Only Subscription having effective billing terms in binding , having one of the selected binding will be retrieved for processing. If no Binding Periods are specified then all Binding Periods are considered as applicable. Specifying Binding Periods is not allowed if the Binding State option is set to any or out of binding
Billing FrequenciesA selection of Billing Frequencies. Only Subscription having effective billing terms with one of the selected Billing Frequencies will be retrieved for processing. If no Billing Frequencies are specified then all Billing Frequencies are considered as applicable
Billing Term SchemesA selection of Billing Term Schemes . Only Subscription having effective billing terms of that scheme will be retrieved for processing. If no Billing Term Schemes are specified then all Billing Term Schemes are considered as applicable
Resting ended X days agoDetermines the Resting Period end date in relation to the date of execution, measured in days. If specified then the process will retrieve Subscription having a Resting Period within the date of execution and date of execution minus the specified number of days. This criterion is optional
Scheduling Settings
Scheduling Settings*

Method - The following options are available:

  • Run Now
  • Run on Specific Date / Time
  • Run Repeatedly
  • Advanced Scheduling

Refer to Scheduler Task for configuration guidelines.

Throttling Settings
ThrottlingThrottling:  It determines the maximum number of processed records that should be affected per each run and the interval between each iteration. This is available only if the repeat and advanced repeat options are selected. Throttling settings include the following
  • Maximum batch size
  • Start again after X UOT (seconds, minutes,hours, days)
Process Runs
Deactivation Run informationDisplays the Runs that were executed for the specific Definition. Each Run includes the Subscriptionthatwere processed.In case of an error, the error code and description is displayed.
Log Information 
Log DetailsThe standard set of Log Details information available in all entities 

Related Areas

Helpful Links

  • No labels