Unanet 3.4 - New Features and Functions

The Unanet 3.4 new features and functions are described in the following sections:

New Unanet Modules -- UnaTime and Una$ense for your PDA

Enhancements for the Unanet Administrator
Enhancements for the UnaTime User

Enhancements for the Una$ense User

Enhancements for the UnaSource User
Enhancements for the UnaPulse Project Manager
Enhancements for the Unanet Manager

Enhancements for the Unanet Customer

 

Important -->  3.4 Impacts to Existing Users  <-- Important


New Modules - UnaTime and Una$ense for your PDA

 

Unanet Technologies has extended access to the Unanet functionality via alternative devices - that is, devices other than a wired PC with a browser.  The initial rollout will include support for entering time and expenses on a Palm Pilot OS™ PDA device.  The new capability allows syncing with the Unanet system. Project information for the PDA user will be copied down to the PDA. The PDA user will enter time and or expenses into the PDA. At any time, the user can sync up the PDA time and expense data with the Unanet server data.

PDA access benefits all levels of the organization. The road warrior will benefit by using time during flights or when access to the Internet is unavailable to immediately record time and expenses. The project manager benefits because immediate capture of data results in better information. Administrators and managers, who must ensure that timesheets and expense reports are approved in a timely manner, benefit because users are able to promptly enter time on the day that timesheets are due.  This new capability is available as a separately purchased module!

 


Release 3.4 Enhancements for the Unanet Administrator


Release 3.4 Enhancements for the UnaTime User

 


Release 3.4 Enhancements for the Una$ense User

 


Release 3.4 Enhancements for the UnaSource User

 


Release 3.4 Enhancements for the UnaPulse Project Manager


Release 3.4 Enhancements for the Unanet Manager


Release 3.4 Enhancements for the Unanet Customer

 


!!  Important  !!

Impacts to Existing Users

Notice to users that use the project import

The file layouts for this import have changed in this version.  If you utilize this import you will need to make adjustments to accommodate for the new field.  A summary of the changes follows:

Notice to users that may have created their own expense types and called them "M&IE_PER_DIEM" or "LODGING_PER_DIEM".

Because we are adding these two new expense types to the system, and they each have a wizard associated with them, if you have already created an expense type that has one of these names, your users will see the new wizard rather than your generic wizard when entering expenses.  If you did happen to have created your own expense types with these names, we would recommend that you rename them prior to upgrading to this version.

 

Notice to users that use time export templates.

The list of database fields available in the time export templates is changing with this release.  In particular, you should note that the behavior of certain existing fields is changing.  In past versions, any of the fields that began with either "PERSON_ORG_" or "PROJ_ORG_" were not picking up the current profile information as you might expect.  Instead, they were returning the 'point in time' values that were saved at the time the timesheet cell entries were saved.  That is, they were behaving as if they were named "TIMESLIP_PERSON_ORG_" or "TIMESLIP_PROJ_ORG_".

With this release, we will be adding a number of additional fields prefixed with the "TIMESLIP_PERSON_ORG_" and "TIMESLIP_PROJ_ORG"  names and changing the behavior of the existing fields to pick up the current related profile information.  You could think of it as though we are renaming the current fields to the timeslip_ name and adding new fields (with the old names) which will result in your having the option to export either the current information or the information that was stored at the time the timesheet was saved.

What does this mean you have to do?  Depending on what data you are expecting to be returned in your time templates -- and -- only if you are using any of the PERSON_ORG_ or PROJ_ORG_ fields, you will need to revisit your time templates and make sure you have the appropriate fields chosen to meet your need.  

This only impacts time templates (not expense, org, project, etc) -- and only those fields that begin with person_org_ and proj_org_.

 

Notice to users that use time export templates.

In addition to the changes mentioned in the previous bullet, we have made several 'behind the scene' changes to the processing of the following fields:

If you were using any of these fields in a custom time template, your template will initially be invalidated after the migration to version 3.4.  If you were to edit this template, and select the "Order" button, you would notice that the field name above would be replaced with the text "null".  This would cause a problem if you attempted to use the template (you'd get a sql exception - column not found).

What does this mean you have to do?  The system will repair the condition if you take the following two steps.  First, edit any field on the template and hit "Save" (you don't have to make any change -- just hitting save will update the template structure).  Second, (and this step is only necessary if you care about the sort order of the output), you would need to hit the "Order" button and re-order the fields according to your desire (you'll notice that the affected field was corrected but placed at the bottom of the list).

This only impacts time templates (not expense, org, project, etc) -- and only those containing the fields listed above.

If you have any questions, contact Support.

 

 

Return to Unanet Table of Contents page


Copyright © 1998-2002 Computer Strategies, Inc., All Rights Reserved.
Last revised: September 13, 2002 .