This topic gives an overview of all the new features added to Replicon for the past several months.
|
Timesheet, Time Off, & Punching |
|
|
Project, Billing, & Costing |
|
|
Payroll & Compliance |
|
|
System |
You can subscribe to have our weekly product updates delivered directly to your inbox. Updates include information on upcoming features, newly-released features and improvements, and bug fixes.
|
CloudClock users can create punches using voice commands, as a way of minimizing touch and the spread of germs in the workplace. If employees use Face ID or QR codes to log in, and voice-controlled punching, they never need to touch the clock. Users can use voice commands to punch in, punch out, and punch in and out of breaks. No other actions, such as entering time off or viewing your timesheet, are currently supported. On-screen indicators show users where voice commands can be used.
To use this feature, you must first enable voice-control for CloudClock. To do this:
Refer to Setting up CloudClock for fore information. Note: Punching against projects, activities, and custom fields is not currently supported. While users can use voice commands to create punches against these items, they’d need to tap to select values, so it would not be a no-touch experience. |
|
|
New timesheet and time off conditional approval rules: Second level supervisor approves |
These new rules will automatically send timesheets and time off bookings to the owner’s supervisor’s supervisor. Refer to Setting up conditional approval rules for more information.
|
|
|
|
The ability to copy timesheet and time off validation rules, and rounding rules |
You can now make a copy of any of the timesheet validation rules, time off validation rules, or punch rounding rules (in addition to timesheet validation rules, which we announced last week). This functionality may be useful in case you want to base a new rule on an existing one, or retain variations of two similar rules. To make a copy of any rule, select the rule on its list page, then click More > Make a Copy:
Or, click the Make a Copy of this Rule link located at the bottom, right-hand corner of the rule’s page.
|
|
To help you more easily find older pay runs, we now include Description and Creation Date filters on the Pay Runs list page of the Payroll Workbench.
|
|
Both Replicon and Polaris PSA administrators can now add, update, or delete skills using the in-app import feature. You can add or modify the name, description, category assignment, and enabled status for each skill via import. |
|
|
If you use Polaris PSA, you can now specify that only approved time billing items are available to bill. The approval status parameter can be set independently for each Time Billing rule you add to a project’s bill plan.
If you don’t update this option, it will remain set to Any (the default), meaning all approved and unapproved time that meets all other bill plan criteria will be available to bill to clients. |
|
|
Ability to use Code as the unique identifier for projects or clients |
In the past, a project’s name always served as its unique identifier in Replicon; that is, the Project Name field allowed Replicon to distinguish each project from all others. That meant the name field had to be unique for each project. But, this caused issues for some of our customers, who integrate with third party tools that use code as the unique identifier, and who sometimes duplicated project names. Now, you can choose to use Project Code as the unique identifier in Replicon, instead of name. If you choose code as the identifier:
Note, the name field is still required since name is used throughout Replicon – names just no longer need to be unique. Also note that this feature applies to clients, too; Client Code can now be set as the unique identifier for clients. You can update project identifiers at:
And client identifiers at:
All existing projects (or clients) must be assigned a unique code before you can change this option. You can use our import tool to easily assign codes. |
|
If two users have the same first and last name, Replicon appends their login name (in brackets) to their full name, so administrators and others can distinguish between the two users. However, this solution doesn’t work well in some cases, such as in SSO implementations that assign an alphanumeric code as the user’s login name. Such codes are hard to recognize or remember. So now, we’re offering a custom display name option you can set up in the user’s profile; it can be their nickname, their department, or whatever helps you identify who they are.
Then the custom name will be appended to the user’s full name, instead of their login name, wherever their name appears.
The loginname will still be appended to duplicate names if you don’t provide a custom name. Note that custom names do not appear where Firstname and Lastname appear in separate fields (e.g. in certain reports and in batch notifications). This feature is available in Replicon and Polaris PSA.
|
|
|
Often, companies only allow employees to access members of their own group. For example, Jim is part of the Accounting department, and is only allowed to share reports with, or assign as substitute, his fellow Accounting teammates. However, if an employee moves from one group to another, their access doesn’t automatically change with them, which makes work for admins, and can cause data security issues if access isn’t updated. Now, you can set a user’s access to automatically update if they change groups by assigning them one of the User’s Location options, rather than assigning an explicitly-named group (e.g. ‘Finance’).
For example, if Jim is assigned one of these new options, and is later moved from Accounting to the Finance team, he will automatically be limited to accessing members of the Finance group. This functionality is available in all products that offer customizable group types. It also applies when assigning time off calendar visibility in user profiles.
|
|
|
We’ve launched a new report template you can use to track and manage your scheduled reports. Among other data, the template includes:
This report can help administrators manage scheduled reports set up by employees who have since left their company.
|
|
|
We offer our API to customers for use in building custom apps and integrations using Replicon data and operations. However, in the past our API documentation wasn’t optimized for customer use, and therefore presented some usability challenges. But now, we’ve completely revamped our API documentation, to make it easier for customers to use. Among the improvements are: A more complete user guide The new user guide includes updated code examples, an easier authentication method, and information on getting started, errors, filtering data, and concepts referred to in the reference documents.
A curated list of services Replicon uses roughly 4000 operations. But, when customers are building apps using our API, they’re typically only interested in a small subset of these. So, we’ve filtered out the operations you’re unlikely to want to use, so you can more easily find the ones you want. But, you can still access all services, if needed. More useful field-level documentation We now offer clearer indications of required fields, more examples, more definitions and explanations, more complete call responses, and information about using operations to filter data. We plan to continue making improvements to these documents based on customer feedback. Each reference page includes a link to a feedback form; please let us know if there are things we can add, or any additional improvements we can make. |
|
|
Ability to limit who can be assigned reports and as a substitute |
In the past, if you set up a substitute user, you could choose any user in the system. Similarly, if you set up a report schedule, you could choose to send the report to any user. And, you could share a report with anyone who had access to that report’s template. Now, to improve data security and promote usability, we’ve introduced an option to limit which individuals a user can select when scheduling or sharing reports, or when assigning substitutes, based on user group assignments. To limit access, select the groups the user can choose from using the Roles and Permissions tab in their user profile. Unlike group limits for other roles, this option does not allow the user to view other users’ items; The user will just be able to share reports with any member of the assigned groups, or set any member as a substitute. If you don’t select any groups for a user, their access won’t be limited. This feature is now available in all enterprise-level products, plus ProjectTime Plus and our ADP products. Refer to Limiting which groups a user can access for more information.
|
|
You can now limit what user data cost managers have access to, using groups. This works the same way other manager visibility limits work – you select which groups a manager should be able to access from the Roles and Permissions tab in their user profile.
This feature is now available in Professional Services Automation, Project Portfolio Management, ProjectTime Plus, and our ADP Premium products. For more information on groups and how to limit access by group, refer to: https://www.replicon.com/help/setting-up-user-groups/ https://www.replicon.com/help/limiting-which-groups-a-user-can-access/ |
