The Nimble BPM Blog

I returned from vacation yesterday and uploaded the new BP Logix Plug-in for MS Word. This latest plug-in version, along with the recent update of the BP Logix software, makes form design more efficient. I so appreciate the “Upload and Leave Checked Out” feature. In the past, we had to make editing changes to a form in MS Word, save and close it, upload it to BP Logix and finally preview the form to determine if the edit was successful. If it wasn’t, we had to download the form to MS Word and begin the process over. With this software version, we can save the edits in MS Word, leave the form open and use the “Upload and Leave Checked Out” feature to examine the form in the preview mode. Since I have two monitors, I can easily edit the form on one monitor while previewing it on the other. I really like this as it makes editing and correcting a form so much easier. Now, I would like to be able to make the edits, save the form, and simply refresh the preview mode to see updates!

UW-Eau Claire forms conversion project—How much can expected of end-users?

In a university environment, resources are always tight and especially so right now during the recession. While our staff has been doing all the forms design as we learn the BP Logix software, at some point, it will be more efficient for departmental designees to assume responsibility for some of the work. The E-form Project Team discusses this frequently and have recently drafted a proposal on the division of labor.

In summary, it reads like this. A unit responsible for five or more forms or less than 5 forms that require many changes or updates, will be asked to name a unit forms designer. This person would create the form in MS Word using the BP Logix Plug in to add fields such as the input and text boxes, the check boxes, radio buttons, drop down fields, and date field. Once this person had the form elements in the order need, and the styles and formatting completed, he/she would meet with a member of the E-forms Project Team and hand the form off for coding of sections, arrays, system variables, if-then logic, etc. Then, once those items were working properly, the form would be passed along to the E-forms Project Team Programmers who would add the workflow, the knowledge view, the email template, etc.

For units with less than five forms or forms that don’t change very often, we are recommending that those units name a point person who works with the LTS E-forms Project Team as the form is designed. We consider this to be efficient use of everyone’s time.