Developer Blog |
We’re happy to announce the launch of BAM version 3.3 for Appway 6.3.
Two major highlights from this latest Appway BAM extension release are the new "Team" dashboard, and new "due date" functionality. For a comprehensive list of new and updated features, please see the full release notes (PDF).
New features in BAM 3.3:
Team dashboard
The BAM dashboards now include a new view on BAM data. In the new dashboard, process activities are grouped according to which team owns that activity. This allows a manager to browse the Active, Completed and Cancelled activities by team, and to check the number of expired and on-time activities for a team.
This view was previously only available at the level of an individual user, and has now been expanded to allow managers to easily extract team-level statistics.
Due Date support
It is now possible to store the due date field of activities in the BAM database, and then use that date in the dashboards for monitoring, filtering and aggregation purposes. By setting a due date on an activity, users can specify a "dynamic" expiration of the activity. The due date can vary from one instance to another.
In addition, while SLAs can only be set as an amount of time starting from the creation of the activity (e.g. "3 hours"), the due date can be a specific date and time (e.g. "Wednesday March 2nd, 3pm"). The due date can be used in addition to, or instead of, the SLA for each activity.
While previous versions of BAM required all activities of the same type to be subject to the same SLA, this new functionality allows you to add an extra level of granularity to your monitoring activities.
Information about how to upgrade from BAM 3.2 to BAM 3.3 can be found in our BAM Migration Guide.
Two major highlights from this latest Appway BAM extension release are the new "Team" dashboard, and new "due date" functionality. For a comprehensive list of new and updated features, please see the full release notes (PDF).
New features in BAM 3.3:
Team dashboard
The BAM dashboards now include a new view on BAM data. In the new dashboard, process activities are grouped according to which team owns that activity. This allows a manager to browse the Active, Completed and Cancelled activities by team, and to check the number of expired and on-time activities for a team.
This view was previously only available at the level of an individual user, and has now been expanded to allow managers to easily extract team-level statistics.
Due Date support
It is now possible to store the due date field of activities in the BAM database, and then use that date in the dashboards for monitoring, filtering and aggregation purposes. By setting a due date on an activity, users can specify a "dynamic" expiration of the activity. The due date can vary from one instance to another.
In addition, while SLAs can only be set as an amount of time starting from the creation of the activity (e.g. "3 hours"), the due date can be a specific date and time (e.g. "Wednesday March 2nd, 3pm"). The due date can be used in addition to, or instead of, the SLA for each activity.
While previous versions of BAM required all activities of the same type to be subject to the same SLA, this new functionality allows you to add an extra level of granularity to your monitoring activities.
Information about how to upgrade from BAM 3.2 to BAM 3.3 can be found in our BAM Migration Guide.

Comments (0)
