Taskflows - adding an Alert/Banner
Wed 19 Dec 2018 - 16:04
Original post by Heather Glassbrook: heather.glassbrook@footanstey.com
We wanted to add an Alert to matters via taskflow. As a simple example, adding an expiry date for OS1 or OS2 search, after capturing through taskflow the date on which the search expires, add an Alert. This would ensure that whoever handled the matter would be aware immediately of this important piece of information. Adding the Alert through taskflow was seamless for the user, they did not have to navigate away from taskflow to, say, the key dates tab or matter notes tab.
However the Alert only lasts for as long as the current session. Below is an example of the script we use. Does anyone know if it is possible to script so that the Alert remains in place until removed later in taskflow or by user? (TR say not)
We wanted to add an Alert to matters via taskflow. As a simple example, adding an expiry date for OS1 or OS2 search, after capturing through taskflow the date on which the search expires, add an Alert. This would ensure that whoever handled the matter would be aware immediately of this important piece of information. Adding the Alert through taskflow was seamless for the user, they did not have to navigate away from taskflow to, say, the key dates tab or matter notes tab.
However the Alert only lasts for as long as the current session. Below is an example of the script we use. Does anyone know if it is possible to script so that the Alert remains in place until removed later in taskflow or by user? (TR say not)
- Code:
FWBS.OMS.Alert alert = new FWBS.OMS.Alert("Priority Expiry Date: " + expiry.ToShortDateString(), FWBS.OMS.Alert.AlertStatus.Amber);
CurrentFile.AddAlert(alert);
Session.CurrentSession.CurrentFile.Update();
FWBS.OMS.UI.Windows.Services.OnOMSTypeRefresh();
Re: Taskflows - adding an Alert/Banner
Wed 19 Dec 2018 - 16:05
Original post by Jamie Francis: jamie.francis@emwllp.com
Not sure why Taskflow removes the alert but you could just update the database field directly, [fileAlertMessage] and [fileAlertLevel] in the config.dbfile table. Something like this should do the trick:
Not sure why Taskflow removes the alert but you could just update the database field directly, [fileAlertMessage] and [fileAlertLevel] in the config.dbfile table. Something like this should do the trick:
- Code:
FWBS.OMS.OMSFile _thisFile = Enquiry.Object as FWBS.OMS.OMSFile;
_thisFile.SetExtraInfo("fileAlertMessage", "Priority Expiry Date: " + expiry.ToShortDateString());
_thisFile.SetExtraInfo("fileAlertLevel", 1);
_thisFile.Update();
Re: Taskflows - adding an Alert/Banner
Wed 19 Dec 2018 - 16:08
Original post by Heather Glassbrook: heather.glassbrook@footanstey.com
Thanks Jamie - we will try this and let you know.
Update:
Unfortunately this would wipe out any other alerts already added by the user in the front end so not really an option for us.
Thanks Jamie - we will try this and let you know.
Update:
Unfortunately this would wipe out any other alerts already added by the user in the front end so not really an option for us.
Re: Taskflows - adding an Alert/Banner
Wed 19 Dec 2018 - 16:16
Original post by Jamie Francis: jamie.francis@emwllp.com
It should be easy enough to append your LR priority bit to the existing alert or check if there is one already and do something else instead.
It should be easy enough to append your LR priority bit to the existing alert or check if there is one already and do something else instead.
Permissions in this forum:
You cannot reply to topics in this forum
|
|