The Clip

We’ve been able to add some functionality to the Timesheet Rules feature. This enables you to automate certain communication (or actions) based on the values of a submitted timesheet. For example, if your company’s policy states that certain departments/employees must submit a minimum of hours worked, then this feature will automate the notification of when/if a particular user fails to meet the requirements. Therefore, both employee and manager can be a little more efficient in the submit and approve pieces of the time tracking workflow.

Here’s a quick guide to setting up rules through the Timesheet Admin console:

1. Add a condition to the rule (also, you can set the order of the conditions to set the appropriate precedence)

2. Select the action which you would like to occur, once a submitted timesheet has met the condition(s) of the rule.

3. Name the Rule, so that you will be able to easily identify it from the Rule List view.

Technorati Tags: officeclip, rules, rules-based Timesheet, workflow

Based on our users feedback we have implemented a field-based access permission for our Web Contact Manager. This allows administrators to provide read, write, delete or append access to a role based on the value of a contact field. For example, if you want to restrict members of Georgia Team only to see the contacts who are in the State of Georgia, you can program this rule in the contact manager at organization level.

OfficeClip Contact Manager has many levels of security; the list below provides a recap of all security levels that can be set for contacts:

1. Organization Level Permission: Allows administrator to set default permission for all contacts in the organization. For example, an administrator can set the system such that only administrators can see all contacts and the contact creator can see only his/her contact.
2. Role Level Privileges: Administrators can create roles and provide privilege for the role users.
3. Role Level Object Permission: Allows creator or administrators to restrict a group of contacts accessible to only a particular role.
4. User Level Object Permission: Allows creator or administrators to restrict a group of contacts accessible to only a particular user.
5. Field-based Object Permission: Rules can be defined in the system so that when a contact is added or edited, permission is controlled based on the value of a field.

Technorati Tags: Contact Manager Tips, rules