Select the node which has no label and, as a Name, enter ‘Price Plan’. In all the tutorials, whenever we create a Price Plan, just give it the same name ‘Price Plan’.

Capture

Right click, Add Component->Rates->Recurring Rate

Capture

Call the Recurring Rate  ‘Monthly Fee’ which is to be triggered on the 1st of every month, at the beginning of the month.

Capture

There is also an Advanced setting which we will not use.

Capture

Highlight the ‘Monthly Free’ node and add a Flat function component to the new branch of the price plan called ‘30 EUR’ and set the Fixed Amount to 30.

Capture

You may realize in the screenshot below, the fixed amount is in TWD currency. Now where did this came from? It came from the Charge. Go ahead and change the description to ’30 TWD’ instead.

Capture

We are done with the Price Plan. The logic tells us that the customer will be charge 30 TWD every 1st day of the Month.

However, the Charge Object still cannot be saved. We have so far created the pricing logic for the rating process, but we have not specified the account to charge against for the charging process. Remember that the Charge Object is responsible for both Rating and Charging.

Simulation of Configuration:

Plan logic can cause an error if it’s not properly configured. The Core Tool provides 3 functions to do a kind of syntax check on you Price Plan Logic. They are the VerifyRead Price Plan and Trial Run Price Plan.

You can find them on the standard toolbar on your Core Tool.

Capture

Capture

Or you can find the in the ‘Action’  DDL.

Capture

When you try to Verify a Charge object on a Price Plan that is not properly configured, the system will point you where the error is occuring.

Capture

When you select the Read Price Plan, the system will translate your Price Plan logic into a human-readable language.

Capture

 

Average Rating
0 out of 5 stars. 0 votes.
My Rating:
Categories:

0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *