A calendar is configured using a worklist, and the results will be displayed in the appropriate day’s cell. These calendars are capable of displaying any worklist data that contains dates: tasks due, invoices billed, tickets created, worker replies, time tracking, worker logins, Twitter etc.

Any number of calendars can now be added to workspaces as tabs.

In this case, the first tab showing the event point was improperly being reloaded, rather than the focused tab. This had to do with page elements not having unique IDs, and multiple owner tabs having the same event point in use. app, role, group, worker) didn’t always refresh the affected part of the page.

Fixed an issue with ‘Setup->Virtual Attendants’ where adding a new behavior on an owner tab (e.g.

The issue was solely with the simulator the actual events always worked properly. This made it difficult to simulate behaviors that looked at related records for example, getting or setting values for the sender as an action during mail filtering. those not set by the simulator’s form) didn’t have any values set. Due to the way that the event works in conjunction with the parser, the underlying fields (i.e.

Fixed an issue with using the Virtual Attendant Simulator on Mail Filtering behaviors.

The report may also be sorted by any of those fields.

Data is displayed for the number of uses for each behavior, along with its total runtime, average runtime, owner, and event. This allows reporting on Virtual Attendant behavior filtered to a specific time period. These stats provide much more insight into how Virtual Attendants are behaving.Īdded a ‘Virtual Attendant Usage over Date Range’ report. Previously, usage stats for Virtual Attendant behaviors were not collected at all. Entries are sorted by a per-day timestamp, each with the number of uses and the cumulative runtime for that time period (which can be used to compute average runtimes). Virtual Attendant usage statistics are now recorded when behaviors run. The ‘defunct’ flag will now be automatically removed from a sender’s record if they send a new incoming message.When editing a bucket, the form will now enforce this maximum length.

Bucket names may now be up to 64 characters in length.This allows VA automation to move the cursor somewhere else (e.g. When replying to mail, the text box is no longer forced as the focused element. Fixed a bug in ticket conversations where sticky notes were no longer displayed for a particular message after minimizing and maximizing it.

Free Simple Sticky Notes 6.3