Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm starting to work with WFA. Trying to build my first workflows I wonder how the "parameters mapping of a command" is working.
Is there some documentation available (besides online help)?
I want to know
- how is parameter mapping used
- what means type, attribute, object name
- what influences do type, attribute, object name have to my workflow
- what happens, if I DO NOT define parameter mappings
- what happens, if I DO define parameter mappings
- where is object name used in the workflow
- can I map (e. g.) a "volume name" parameter to a type of storage.lun and attribute volume.name with an object name of "LUN"? And what causes this to my workflow?
Thanks for your help!
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Let me provide some details on what command parameter mapping means and guidelines on its usage.
This is something we refer to when designing certified commands released in WFA.
Note: There will be exceptions to these guidelines depending on the design of the command.
Hope this helps.
Thanks,
Shailaja
1.1.1 Command Parameter Mapping Guidelines
A command has a number of parameters and they are mapped in “Parameters Mapping” tab when you edit a command. This mapping has to be done based on the following guidelines.
- Command parameters are mapped to specific attributes and references of dictionary entries.
- Command parameter mapping defines the way the parameters to execute a command (CommandDetails - rectangular boxes you see in the designer) will be defined in the workflow.
- All mapped command parameters appear in different tabs during workflow design for that command’s details and the tab will be named according to “ObjectName” in the command mapping definition.
- All unmapped parameters appear in the “Other parameters” tab of the Command Details in the simplified designer.
The rules for mappings of command parameters to dictionary entries and its attributes have been derived based on:
- Commands can generally be categorized into different categories from the perspective of the functionality it supports. The mapping of command parameters depends on the type of functionality the command supports.
- Depending on the way the command will be represented in the workflow designer.
Example Command parameter mapping and the way it is displayed in workflow designer.
# | Command Category | Rules for mapping |
1 | Create a new object General flow of usage:
|
|
2 | Update an object General flow of usage: Find object and update attributes |
|
3 | Remove object General flow of usage: Find object, Delete it |
|
4 | Commands dealing with optional parent and child objects. |
|
5 | Updating/Add/Removing associations between objects |
|
3 REPLIES 3
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Let me provide some details on what command parameter mapping means and guidelines on its usage.
This is something we refer to when designing certified commands released in WFA.
Note: There will be exceptions to these guidelines depending on the design of the command.
Hope this helps.
Thanks,
Shailaja
1.1.1 Command Parameter Mapping Guidelines
A command has a number of parameters and they are mapped in “Parameters Mapping” tab when you edit a command. This mapping has to be done based on the following guidelines.
- Command parameters are mapped to specific attributes and references of dictionary entries.
- Command parameter mapping defines the way the parameters to execute a command (CommandDetails - rectangular boxes you see in the designer) will be defined in the workflow.
- All mapped command parameters appear in different tabs during workflow design for that command’s details and the tab will be named according to “ObjectName” in the command mapping definition.
- All unmapped parameters appear in the “Other parameters” tab of the Command Details in the simplified designer.
The rules for mappings of command parameters to dictionary entries and its attributes have been derived based on:
- Commands can generally be categorized into different categories from the perspective of the functionality it supports. The mapping of command parameters depends on the type of functionality the command supports.
- Depending on the way the command will be represented in the workflow designer.
Example Command parameter mapping and the way it is displayed in workflow designer.
# | Command Category | Rules for mapping |
1 | Create a new object General flow of usage:
|
|
2 | Update an object General flow of usage: Find object and update attributes |
|
3 | Remove object General flow of usage: Find object, Delete it |
|
4 | Commands dealing with optional parent and child objects. |
|
5 | Updating/Add/Removing associations between objects |
|
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your reply.
This answers my questions but opens a lot of new ones. For example:
- what are dictionary objects and how are they used
- attributes/references to dict. objects?
- how to choose the right dict. object?
Is there more documentation available (point 1.1.1 implies that there is more)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
- what are dictionary objects and how are they used
- attributes/references to dict. objects?
- how to choose the right dict. object?
A dictionary entry is the definition of an object type that is supported by WFA. Each dictionary entry
represents an object type and its relationship in the supported storage and storage-related
environments. A dictionary object consists of a list of attributes, which might be type checked, and a
dictionary object with complete values describes an object instance of a type. In addition, the
reference attributes describe the relationship of the object with the environment; for example, a
volume dictionary object has many attributes, such as name, size_mb, and volume_guarantee. In
addition, the volume dictionary object includes references to the aggregate and the array containing
the volume in the form of array_id and aggregate_id.
Also, the video in https://communities.netapp.com/videos/3151 provides some details.
Is there more documentation available (point 1.1.1 implies that there is more)?
[Shailaja] There will be more documentation on this area as part of 2.1 WFA release which will be in a few weeks.
Thanks,
Shailaja