After you create an Ant Cube Card and add card resources, you must release the card so that clients can pull it. You can create a release task for an Ant Cube Card in the mPaaS console.
Prerequisites
To use the whitelist release model, create a whitelist before you release the card.
For more information about how to create a whitelist, see Whitelist management.
Procedure
-
Log on to the mPaaS console and select the target application from the application list.
-
In the navigation pane on the left, choose Mobile Delivery Service > Ant Cube Card > Card Management to open the Card Management page.
-
On the Card Management page, click the card that you want to release in the Card List.
-
Click the Create a Release button to open the Create a Release page.

-
On the New Release page, configure the following parameters and click Submit.
-
Release Type: required. Select grayscale release or official release. Grayscale release allows you to configure the release model, whitelist, and advanced rules. Official release does not require these configurations.
-
Release Model: required. Select whitelist or time window.
-
Whitelist: Releases the card only to users on a specified whitelist.
-
Whitelist Configuration: If you select Whitelist as the release model, select a pre-created whitelist.
NoteIf a selected whitelist contains more than 100,000 users, only the first 100,000 users are included.
-
-
Time Window: Performs a canary release to a limited number of users within a specified time period.
-
If you select the Time Window model, specify the window closing time and the number of users for the canary release.
-
-
-
Release Description: optional. A description of the release task.
-
Advanced Rules: optional. Release the card based on specific rules. You can configure Platform, Type, Operation Type, and Resource Value, as shown in the following figure.

-
Type: required. Supported types include city, model, network, and device system version.
-
Operation Type: required. Select contain or not contain. For the device system version type, additional in-range and out-of-range options are available.
-
Resource Value: required. Enter the resource value directly, or use a preconfigured resource mapping from the release rule.
-
For more information about how to add resource values for advanced rules, see Release rule management.
-
-
After the card is released, the task status changes to "In releasing" as shown in the following image. You can view, pause, or end a task that is in the "In releasing" state. While a card version has an active "In releasing" task, you cannot create another release task. Wait for the current task to finish, or end it before creating a new one.
