Creating or removing Interactions can now be done outside the CMS via the BMP CLI.
Create interaction
| Code Block |
|---|
|
blinkm bmp create interaction <name> --type<type> --remote |
...
| Info |
|---|
|
Created Interactions will not appear on the BMP until deployed,except for --remote which will add a place holder on the BMP |
Create interaction Examples
Here is an example of the BMP CLI workflow on a sample answerSpace called "myanswerSpace"
First we will pull the empty answerSpace down from the BMP.
| Code Block |
|---|
|
blinkm bmp pull |
Here is the view from the BMP CMS, no interactions are yet created.
Now we are ready to start creating interactions.
| Code Block |
|---|
|
blinkm bmp create interaction default |
...
| Info |
|---|
As the interaction type was left blank, the interaction "default" was create as a madl type |
Lets now create a "message" interaction using the – type option
| Code Block |
|---|
|
blinkm bmp create interaction message --type message |
Now lets create an interaction using the --remote option
| Code Block |
|---|
|
blinkm bmp create interaction myinteraction --remote |
...
| Info |
|---|
|
Note because we used --remote an empty interaction place holder now shows in the BMP CMS. This method is ideal when wanting to reserve a unique name when developers are using both CMS and CLI at the same time. |
Lets now deploy the interactions to the BMP
| Code Block |
|---|
|
blinkm bmp deploy |
Editing interaction files
In every interaction directory is a file called <interaction name>.json
...
| Item | Description | CMS Label | Options |
|---|
| display | Hidden items are not displayed in lists but are otherwise still accessible | Display | hide / show |
| displayName | Caption or title to display to users | Display Name | |
| status | Inactive items are hidden and treated as though they do not exist | Status | active / inactive |
...