Celoxis 11.1 — the complete Knowledge Base

Project states enable you to define and track the project lifecycle from initiation to closure. By default, we provide the following states: Draft, Active, Canceled, On-Hold, Archived; but you can customize them to suit your business.

States also allow you to control some aspects of system behaviour. For example, you could disallow logging time for projects in the Draft and Archived project states.

System behaviour is also different based on the project state's stage.

Project stage

Every project state must belong to one and only one of the following project stages: Planning, Execution and Closure. The system will behave differently for projects based on the stage its project state represents as described below:

For example, if you define a project state called Unapproved and set its stage to be Planning, then any project in the state Unapproved will not have RAG indicators nor will it generate email notifications. However, any work exceptions added for work calendars or resources will result in the project plan to be recalculated.

Using project states

A project may belong to only one project state.

Project state can be set on the add/edit project screen under the Custom Fields tab. To modify project state for many projects at once you can use the bulk edit screen.

Project states can also be used in columns, filters, groups, and charts.

Managing project states

Only administrators can manage project states. To manage project states navigate to AdministrationProject Management sectionProject States

If you do projects that are similar in structure, then instead of building your project plan from scratch every time, you can create and save those projects as templates to get a new project up and running quickly.

Using project templates

To create a new project from a template, click Main MenuAddProjectUse a Template

Managing project templates

Only administrators can create and manage project templates.

A template can be created from any project. To create or manage project templates, navigate to AdministrationProject ManagementProject Templates

Project types help you categorize your projects. Using our reports, you can get important KPIs like profit, effort and margin aggregated for your project types, thus helping you understand business performance.

You can also setup custom fields specific to your project types to capture relevant business data.

For example, a legal firm may have project types such as Bankruptcy and Patents. Custom fields could be Insurance Company and Loan Number for the former; and Patent number, Patent Sponsor and Patent state for the latter.

Using project types

A project may belong to only one project type.

Project types can be set on the add/edit project screen under the Custom Fields tab. To modify project type for many projects at once you can use the bulk edit screen.

Project types can also be used in columns, filters, groups, and charts.

Managing project types

Only administrators can manage project types. To manage project types navigate to AdministrationProject Management sectionProject Types

Clients are individuals or organizations for whom projects are executed. Associating clients with projects helps in filtering, reporting, charting, and in many other areas.

In addition, you can give your clients access so that they can login to view reports shared with them, engage in online discussions, share files and even participate in business workflows (e.g. bugs, change requests and approvals).

Client access is free.

Client Login

Virtual clients are clients that do not have a username and password. They cannot log in to Celoxis. When you create a client, you can optionally assign it a username and a password. You can also set their login credentials from the edit client screen.

If, at a later time, you wish to withdraw login access, simply blank out the username and password for that client.

To prevent any accidents, clients are not notified about their usernames and passwords. It is up to you to communicate their credentials to them.

Client privileges

Every client account can be configured to have the following privileges:

Allow client to view task information, excluding financial information: This determines whether clients can view task details. Financial fields (including custom fields) are never shown to the clients.

Allow client to view details of progress update on tasks: This determines whether clients can view updates and comments on the task.

Allow client to do progress update on tasks: This determines whether clients can add comments on a task.

If you share reports with your client, then the above privileges override the data shared in reports. For example, if you share a task list report to a client that does not have the Allow client to view task information… privilege, then that client will see an empty report.

Client Hierarchy

Consider the following scenarios:

• More than one person from a client organization wants to collaborate on a project.
• Your company does projects for different departments (or branches) of a client, but executives want consolidated reporting. For example, your company may do projects for IBM India and IBM France and your CXOs may want a consolidated report for IBM. Also, you don’t want people from IBM India to access IBM France’s projects and vice-versa.
• You want to prevent accidental access of one client to another’s project. For example, you do not want to give CBM access to IBM’s projects because of a typo.

That’s where the concept of Client Hierarchy comes in. Celoxis allows you to create client hierarchies for better reporting, collaboration and access control.

Example

Consider the following clients:

 1    Peter Parker

 2    IBM
 3    ├── John
 4    └── Alisha

 5    Acme 
 6    ├── Acme (France)
 7    │   ├── Pierre
 8    │   └── Chloe
      │
 9    └── Acme (India)
10        ├── Ravi
11        └── Suresh

There are a total of 11 clients.

Peter Parker is an individual client. There is no hierarchy.

IBM has two child clients - John and Alisha.

Acme has two child clients - Acme (France) & Acme (India), each having two child clients - Pierre and Chloe for the former and Ravi and Suresh for the latter.

To create this parent-child relationship, use the “Parent” field from the add/edit client screen.

Project Visibility

When you assign a project to a client, it is visible to that client and all its descendants. Continuing with the above example:

Setting project clients

You can set a project's clients from the project's add/edit screen or from project bulk actions. The first client becomes the project's primary client

Clients Reports and Dashboards

You can share reports and dashboards with clients. You can share tabular, pie charts, bar charts and many other views of reports. For more information, read the chapter on dashboards

To share it with a client, select the client in the Visible to Clients field in the add/edit report form. If you pick the All option, the report will be shared with all clients.

You can also control which project tabs are visible to clients in a similar way. Navigate to AdministrationProject ManagementProject Views, edit the view and select the clients as described above.

For more information on report and dashboard sharing, read the chapter on report sharing.

Note that clients can modify filters that are marked as promptable in the report's filter tab.

Financial data is never displayed to clients even if those columns are accidentally selected.

Client Actions

Clients can actively collaborate through the system increasing transparency and reducing duplicate work. It also helps maintain an audit trail and ensures things don't fall through the cracks.

Viewing clients

Clients can be viewed by admins and those users having the View Client privilege.

To see the client list, go to Main MenuViewClients

Creating clients

Clients can be added by admins and those users having the Add Client privilege.

To add a client"

1. Click Main MenuAddClient
2. In the Basic tab:
   1. Fill in Name, Email, and Phone number.
   2. If the client account is part of a hierarchy, enter the parent.
   3. If you do not wish the client to have a login, enter login and password, click on the virtual checkbox.
   4. Assign appropriate privileges.
3. In the Custom Fields tab, fill in the appropriate custom fields.
4. In the Preferences tab, select the appropriate locale, date formats and dashboards.
5. Check the Add Another check box if you wish to add more clients.
6. Submit

Login information is not sent to the client.

Importing Clients from CSV

Celoxis provides you with the ability to import clients from CSV. If you have a Microsoft Excel file, then you can export it in CSV (comma separated values) format and then import it in Celoxis.

To import clients, go to the clients page – Main MenuViewClients and then click on the Import button. Upload the client in the format described below.

Fields supported:

• Name - mandatory
• Email
• Phone
• Username - the login name.
• Password - the plain text password.
• Virtual - false or true to indicate whether the client can login or not respectively.
• Custom Fields - you will have to create the fields in Celoxis first

Clients are

notified of their login accounts.

A project team is a set of users who work on a project. The main advantages in defining a project team are:

1. Convenience - you will see only the users in your project team while assigning tasks to users.
2. Security - you can assign special privileges to users in the project team. For example, you can configure the system such that any user in the project team can comment on any task in the project.

Defining a project's team

Project team can be set on the add/edit project screen under the Advanced tab.

A few rules to remember:

• Project managers defined for the project are always part of that project's team.
• Users assigned to tasks in a project are always part of that project's team.

Enabling project team capability

To enable the project team capability, navigate to AdministrationProject ManagementProject Options and uncheck the When assigning tasks, show all users... option.

For small teams, this capability may be an overkill and is better to disable it.

Celoxis is a great alternative to Microsoft Project. Celoxis' integration with Microsoft Project is one of the most comprehensive in the industry. If you understand how it works, you can achieve a perfect 2-way synchronization with Microsoft Project thus getting the best of both worlds.

Importing from Microsoft Project

You can create a project directly from a Microsoft Project file (Main MenuAddProjectImport Microsoft Project) or import tasks into an existing project (Project ActionsImport from Microsoft Project).

When you import a Microsoft Project file (XML or MPP), Celoxis will import:

• Parent-child relationships
• Dependencies including lead-lag times
• Constraints
• Resource assignments
• The default baseline

What is not imported:

• Calendar options - e.g. hours/day, days/month, etc.
• Resource list
• Custom fields
• Non-default baselines
• Calendars and exceptions
• Time-phased data

Import field mappings

While the field mappings in most cases are self-explanatory (they have the same name in MS Project and Celoxis), some fields deserve a special mention:

Understanding Deviations

Celoxis and Microsoft Project while similar in many ways are different in certain areas (see the list of what is not imported above) and that can cause certain surprises. If dates do not match in Celoxis after importing, ensure that:

• Work calendars and exceptions in MS Project and Celoxis match. Note that MS Project does not support time-zones or fractional non-working times.
• You are not using any of the options or features in Microsoft Project that Celoxis does not import
• You mapped the resources correctly during the import

Exporting to Microsoft Project

When you export a project to Microsoft Project (Project ActionsExport to Microsoft Project), the following will be exported:

• Parent-child relationships
• Dependencies including lead-lag times
• Constraints
• Resource assignments
• The default baseline
• Work Calendars and Exceptions
• Resources and their individual exceptions

What is not exported:

• Custom fields
• Inter-project predecessors
• Fields that have no corresponding field in Microsoft Project (e.g. workspace, budget, etc.)
• Resource allocation in hours is changed to % because Microsoft Project does not support allocation in hours

Export field mappings

While the field mappings in most cases are self-explanatory (they have the same name in MS Project and Celoxis), some fields deserve a special mention:

Understanding Deviations

Celoxis and Microsoft Project while similar in many ways are different in certain areas (see the list of what is not exported above) and that can cause certain surprises. If dates do not match in Microsoft Project after exporting, ensure that:

• Work calendars and exceptions in MS Project and Celoxis match. Note that MS Project does not support time-zones or fractional non-working times.
• You are not using any of the options or features in Microsoft Project that Celoxis does not import
• You have not allocated resources in hours and only used % in Celoxis. Microsoft Project does not support allocation in hours.

RAG stands for Red, Amber and Green. RAG indicators visually indicate the health of projects or tasks with respect to schedule and cost.

Celoxis automatically calculates the RAG indicators for projects and tasks regularly if the project's is in the Execution stage. Otherwise, the RAG indicator is shown as Not Active.

Schedule RAG Indicators

For every project and task, Celoxis automatically calculates its projected finish date based on the current rate of progress once a day. It is the date on which the project or task is likely to finish based on the current rate of progress.

For example, say a task was scheduled to complete in 4 days and after 2 days it is only 25% complete. Celoxis will calculate the projected finish date of the task to be the 8th day instead of the original 4th.

For a project or summary task, its projected finish date is the maximum of the projected finish dates of its leaf-level tasks.

RAG indicators are assigned as follows:

Cost RAG Indicators

For every project and task, Celoxis automatically calculates its projected cost based on the current rate of spend once a day. It is the cost the project or task is likely to incur based on the current rate of spend.

For example, say a task's budget is $1000 and it is 25% complete with an actual cost of $200. Celoxis will calculate the projected cost of the task to be the $800 instead of $1000.

For a project or summary task, its projected cost is the sum of the projected cost of all its leaf-level tasks.

RAG indicators are assigned as follows:

If budget is unspecified, the planned cost will be used instead while calculating the RAG status.

Calculation of Projections

Calculating projections is a resource intensive operation hence it is infeasible for the system to maintain RAG indicators in real-time.

Celoxis calculates projections once a day on a best effort basis. However, you can ask the system to recalculate projections for a project anytime using Project ActionsRecalculate Projections. You can even recalculate projections for multiple projects using Project Bulk ActionsRecalculate Projections from your project list view.

A work calendar defines the working and nonworking times for an organization. It specifies the work hours for each work day, the work days for each week, and any exceptions, such as holidays.

You can define many work calendars each with its own time-zone, working hours and exceptions.

Work calendars are used in scheduling tasks.

Using Work Calendars

Every user must belong to one and only one work calendar. Work calendar can be set for a user from the add/edit user screen or from the bulk edit screen.

Every project has a default work calendar. All dates on its interactive Gantt chart are shown with respect to this work calendar's time-zone. The default work Calendar can be set for a project from its add/edit screen.

Managing Work Calendars

Only administrators can manage work calendars. To manage work calendars, navigate to AdministrationProject ManagementWork Calendars

Exceptions

Exceptions are times that are an aberration to the rules defined in the work calendar. Exceptions can be defined for the entire organization (e.g. Christmas holiday), for work calendars (e.g. 4th July holiday only in the U.S.) or for individuals (e.g. Joe is going on a vacation from 3rd to 10th May 2016).

When exceptions are added, modified or deleted, task dates are recalculated. For example, if Mark is sick on a 3rd May and a work exception is entered, all tasks that Mark was supposed to work on 3rd May will be pushed a day ahead.

Working and Non-Working Exceptions

While most exceptions are non-working, you can also enter working exceptions. For example, if Peter is going to work on a Saturday, the 10th of June, you can enter a working exception for Peter on 10th June and all tasks assigned to Peter will be rescheduled appropriately.

Managing Exceptions

Only administrators can add organization wide or work calendar exceptions. To manage exceptions, go to AdministrationProject ManagementWork Calendars and click on the Exceptions tab.

To create a project, click Main MenuAddProject

Blank Project

This creates a project with no tasks.

Copy Project

This clones the project and its entire task WBS. All project and task fields (including custom fields but excluding constraints), dependencies, resource assignments and file attachments are also copied. The new project is then replanned as per the new project's start date. If the original project had manually scheduled tasks, those tasks in the new project will have a similar duration and will start at the same time after the new project's start.

Use a Template

For more details, click here.

Import Microsoft Project

For more details, click here.

You can attach file or files from your local drive or Google Drive to a project's folder. Click on a project to open its panel and then click Project ActionsMoreAttach Files. Files attached to a project (or its tasks) can be viewed from the Files tab.

Depending on whether you use user-based billing or time code based billing, either the default bill rate for a user or time code is used while calculating the bill amounts. You can override those rates per project.

To override the default rates, click on a project to open its panel and then click Project ActionsMoreBilling Rates.

In the above example, Ellen Ripey's bill rate for the project has been set to $150. As you can see, you can click on the Add button to add a rate, click on the Rate cell to edit a rate, or click on the icon to delete a row which will default the rate for that user back to the default rate.

By default, the labor cost rate specified for a user is used while calculating the labor cost of a task. You can override those rates per project.

To override the default rates, click on a project to open its panel and then click Project ActionsMoreCost Rates.

In the above example, Ellen Ripey's cost rate for the project has been set to $50. As you can see, you can click on the Add button to add a rate, click on the Rate cell to edit a rate, or click on the icon to delete a row which will default the rate for that user back to the default rate.

Celoxis provides you with the ability to import clients from CSV. If you have a Microsoft Excel file, then you can export it in CSV (comma separated values) format and then import it in Celoxis.

To import clients, go to the clients page – Main MenuViewClients and then click on the Import button.

Fields supported:

• Name - mandatory
• Email
• Phone
• Username - the login name
• Password - the plain text password
• Virtual - false or true to indicate whether the client can login or not respectively. If you specify false or blank, then you must provide a username and password
• Custom Fields - you will have to create the fields in Celoxis first

For security reasons, no emails are sent to clients. It is up to you to notify them of their login information.

You can select multiple projects and perform actions on them. Click on the next to the checkbox in the report table header as shown below:

Recalculate Projections

For details, refer the Calculation of Projections section here

Edit

Allows multiple attributes to be modified at once, including custom fields as shown below:

Portfolio management, often referred to as project and portfolio management or PPM isn’t as complicated as one might think. Using Celoxis, you can initiate project requests, develop project scoring model, view project request queues and available resource capacities, achieve desired portfolio balance and track project pipelines and portfolio accounting so that you are always staying ahead of your projects.

Setup

1. Enable Portfolio feature in your account (AdministrationProject ManagementFeatures).
   This enables the Portfolio section in Projects to capture Alignment, Benefit and Risk parameters for the portfolio. These are the standard attributes we provide for portfolio management.
2. Create a new Project State ‘What-if’ (AdministrationProject ManagementProject States).
   Keep this state in ‘Planning’ Stage and keep ‘Allow Time’ unchecked. We will use this state to perform rudimentary what-if analysis to arrive at a desired portfolio balance.
3. Import the Project Approval App. (AdministrationCustom AppsAppsImport).
   With this you get a standard out-of-the-box project request workflow. You can customize this workflow to suit your business process. Edit the app and uncheck the “Active” checkbox under Basic tab. This way the app is not available to your users till we set up the rest of the pieces.
4. Develop your Project Scoring model.
   Define the additional project attributes that will be potentially important factors to scoring projects. This will be done through custom fields (AdministrationAccount ManagementCustom Fields). Attach these custom fields to all Project Categories and also to the Project Approval App.
   In addition to your specific project scoring attributes, you will also need to create the following 3 custom fields and attach them only to the Project Approval App:
   • - Strategic Alignment (Numeric: 1 to 100),
   • - Overall Benefit (Numeric: 1 to 100), and
   • - Project Risk (Single-select Drop down: Very High to Very Low).

   These are required to match the standard portfolio parameters on the project, so that you can later copy them into your project. Lastly, create a custom formula field “Project Score” that will take in these project attributes and arrive at a potential score for the new project.

5. Create a ‘Project Requests Queue’ report for viewing your incoming project request pipeline (ReportsAll ReportsNew ReportProject Approval).
   In the Output tab, select ‘Tabular’ and choose all columns that are important for your executive approval. Make sure to include the “Project Score” in the list so that you can directly see the calculated score for each project request in the pipeline.

New Project Requests

Each new project enters the system through a project approval request. The ‘Project Queue’ report that we created comes handy in viewing the incoming project requests and ranking/re-ranking them based on your criteria.

1. Go back to your Project Approval App definition (AdministrationCustom AppsApps) and mark this as “Active”. Now this app is available to your users for submitting new project requests.
2. For each of your new projects, create a project approval request in the system (AddProject Approval).
   Since a project container is not created as yet, create this app within a workspace (if you have defined workspaces) or select non-project (if there are no workspaces in your company). You will have to establish scoring values for each project request and put them in the respective custom fields on the New Project Approval form.
3. As your request is approved, you will need to create a project container for your new project (AddProjectNew Project).
   Enter the necessary information (such as tentative start date, client, budget, etc.) about this new project in the form. Keep the project in ‘What-if’ state. This way it does not interfere with your other active projects. Additionally, copy over all the scoring parameters from the project approval request into the project’s portfolio section and the defined custom fields.
4. Now move the project approval request associated with this new project under the project itself (Go to the said Project Approval itemMoreMove and select the new project from the list). This way, the approved request stays within the project’s repository.

Desired Portfolio Balance

Now that you have created all your project containers, you will need to validate them against your available resource capacities and revise them based on resource availabilities, priorities and strategic importance.

1. Check available resource capacities. Go to ReportsAll ReportsResource Capacity. This is a built-in report that gives you insights into your organizational resource capacities for the near future. Looking at this report you can get a good idea of how your existing resources are stacked up to take in the new projects in your portfolio. You can increase the default period in the report to get farther insights into your resource capacities. You can also search for resources with specific skillsets by using the “Resource: Search” filter.
2. Now, for each project, define the WBS and resources. Since the project is in ‘What-if’ state, it will not affect your existing project workload. Open the Resource Load View (ViewResource Load). From the filters, add ‘What-if’ to your Project State filter. Now your Resource load will start showing your new projects in addition to your draft and active projects.
3. Use the Resource Load View to conduct a rudimentary what-if analysis to understand the impact of your new projects onto the existing resource load.
4. From the Resource Load View, you can
   Check if there are any resourcing problems You can replace resources, if necessary. Mouseover the task in contention, and select the 3-line menuEdit Resources. You can also shift out tasks by changing their dates (Mouseover task3-line menuEdit Task)
5. If you still have a resourcing issue, change the start date of the other low priority projects so that all other tasks in those projects are rescheduled. However, please note that Celoxis does not currently support an UNDO feature. If you need to revert, you will have to manually revert the project to its earlier state.

Portfolio Reports

Celoxis gives our several best practices portfolio reports for managers and executives that you can use out-of-the box. You can also create your reports.

1. Budget Allocations

   This is a bar chart report that lays out budget allocations per manager aligned by their projects’ start month and year. This gives a visual insight into your approved budget allocations for managers and their projects.

   

2. Project Portfolio Analysis

   This bubble chart gives you a good 30,000 feet overview of how your projects are aligned with organizational strategy and financial or operational benefit. The color coding on the bubbles indicates the perceived risk from the project.

   

3. Projects (By Schedule)

   This is a tracking report that gives you an overview of all projects in your portfolio and their schedule status.

   

4. Project Status (Gantt)

   This is timeline view of all projects in your portfolio. Again a tracking report, and gives managers and executives a good overview of how the projects and their top-level tasks are lined up with their schedules.

   

5. Cost Overrun

   Cost Overrun is a tabular report that identifies projects whose actuals costs have exceeded their estimated costs.

   

6. Resource Capacity

   With this time-phased report, executives and project approvers can get a clear picture of your resource capacity at any point and make better resourcing decisions for new projects.

   Estimated Capacity (%) = 1 − Estimated UtilizationActual Capacity (%) = 1 − Actual Utilization

   

7. Resource Utilization

   This report can help track the utilization of resources against the plans.

   Estimated Utilization (%) = Estimated Hours ÷ Hours (Available)Actual Utilization (%) = Actual Hours ÷ Hours (Available)

   

8. Resource Efficiency

   This is an excellent report for monitoring resource performance.

   Efficiency (%) = Estimated Hours ÷ Actual Hours

   

Cost is one of the important components of the project management triangle. Celoxis makes it very easy to track budgeting and costing for entire projects, as well as the individual tasks. After following this simple how-to manual, you will be able to easily arrive at the realistic project budget, keeping an eye on the breakdown budgets of the individual tasks. You will also learn, among other things:

• How to specify Fixed and Material cost of each task
• How to properly allocate human resources
• How to track financial state of the projects and tasks through important metrics like Project/Task Estimated Cost, Actual Cost and the Visual Health Indicators.

Arriving at your Project’s Budget

To Budget for a project you must first know what it will cost to execute the project. Once the execution value is established, add a buffer, and a desired margin (if applicable) and you will arrive to a realistic budget figure. Here is how you do this:

First, for each resource you specify a Cost Rate per hour. This will typically be the salary you pay the resource or it could be an hourly rate for a contractor.

The next step is to create the tasks for your project and assign resources to each task. Celoxis then automatically calculates the cost of the task based on the Cost Rate and the allocated effort of the resource. For example, if Alison’s rate is $50phr and she is projected to work for 10 hours on a given task the cost will be 10*50 = $500. If John (another resource) was to also work on this task, his cost would be added as well. Combined, the costs of Alison and John will constitute the task's labor cost.

Now let’s say you had to purchase computers worth $1000 for the task #2 on the figure above. You can enter this amount in the Planned Non-Labor Cost field for a task.

Now the Planned Cost of this task will be $1500 (i.e. $500 + $1000)

Once you complete this activity for all tasks in your plan, the total sum of Planned Costs of all the tasks will be the Planned Cost for the project. You will use the Planned Cost as a base for the budget of your project.

To see the project’s Planned cost, turn to the Financials section of the Project Details tab.

Add your buffer/desired margin to the Planned Cost to set the project’s budget.

Tracking Actual Costs

When the work on the project begins, and through the duration of the project, all resources will be filling their timesheets to log the actual hours they spend on each task. Once these hours are approved by the manager, they are used by the system to automatically calculate the Actual Cost of each task. For the non-labor cost, such as the purchase of computers, a resource must add Expenses to the corresponding tasks. The expenses will constitute the Actual Material Cost of each task, and will be added to the overall Actual Cost. Just like in the case of the logged hours, each expense will need to be approved by the manager before it can be factored into the Actual Cost of the task.

Displaying the appropriate columns in the Interactive Gantt will allow tracking of the Budget Status of each task, along with the Actual Effort.

As your team updates status on tasks and log hours or expenses, Celoxis automatically and instantly calculates the Projected Cost for each task. This allows the “early warning” mechanisms such as Budget Health RAG indicators to warn you beforehand if your costs are going to exceed the budget (or estimates). For example, if a task is 50% completed, and has already incurred the cost of $100, then the projected cost of the task is $200.

RAG indicator for the budgetary health of tasks (and for the project)

• Off Track - if the Actual Costs exceeds the Budget. If Budget is not specified, then it considers the Estimated Cost.
• On Track - if the Projected Cost is less than or equal to the Budget (or Estimated Cost, if Budget is unspecified).
• At Risk - if the Projected Cost exceeds the Budget (or Estimated Cost, if Budget is unspecified).

This makes it easy to track the budget status for each task individually. However, in most cases you are likely to be more concerned about the overall health of the project. This information is always conveniently displayed next to the project name.

For the basic metrics of the Project’s financials, turn to the Financials section of the Project’s Detail tab.

Manager and Executive Cross-project Reports

Below are just few examples of the helpful and easy-to-generate reports which can additionally inform you about budget allocations, actual costs and other financial aspects across multiple projects. Each report can be easily configured, grouped, ordered or turned to a visual chart to your liking.

Other Scenarios

1. My projects have a pre-allocated budget. Can the system alert me when the planned costs risks exceeding this value?

   Yes! Set the project’s budget in the Advanced tab of the Edit Project dialogue, and watch for the financial health indicator of the project. The RAG indicators will warn you if the project’s budget will get off track.

2. Some of my tasks incur a fixed fee. How do I account for it?

   Make sure to add the Fixed cost under the Advanced tab if the Edit Task dialogue. Then the cost of the task will be calculated automatically when you update the completion progress. For example, if the fixed cost is set to be $1000, and the task is %30 completed, the Actual Cost of the task is %30 of $1000 = $300.

3. Some of my tasks may have a budgetary cap which should be met, regardless of who handles the task. How to set this up?

   Same as with the budget of a project – set the budget under the Advanced tab of the Edit Task dialogue, then watch for the RAG health indicators. Make sure to display the Budget Status column in your Interactive Gantt to keep the status of each individual task visible.

4. We don’t book our resources in the initial project validation stage. How can I arrive at estimated costs with knowing my resources?

   Create “virtual” users such as Project Manager, Graphic Designer, Web Developer, etc. Set each virtual user with the appropriate cost for the given role. Allocate the work for the virtual users - this will help you to arrive at the projected cost of the project. Once the project team was named, use the Resources >> Replace a resource function of the Interactive Gantt to replace each virtual user with the actual resource. Note that the allocated hours will remain intact after the replacement.

5. We have different resource rates for certain projects. How can I achieve that?

   You can specify the project-specific cost rates for every user and for every project using More >> Cost Rate function. If the cost of the user is not specified for the project, it will default to the cost set in the Edit User dialogue.

6. What happens when there is a cost adjustment to resources with projects in progress?

   The cost for the work already performed will be calculated at the previous rate. The cost of all future work will be calculated using the new rate.

7. How do I account for an unplanned expenditure on my project?

   Any unplanned expenditure should be added as an expense to an appropriate task(s) of the project. For example, let say that per manager’s approval a resource has purchased a single-user license for a graphic editing software. The cost of the license should then be added to the very task that the software will be used on. Note that the expense will need to be approved by the Project Manager before it can be factored into the cost of the task.

8. Can I categorize the activities and expenses incurred across my projects for management reporting?

   Yes. Multiple time and expense codes can be set by the Celoxis administrator in the Timesheet and Expenses sections of the Administration page. Typical expense categories may include Travel, Meals, Office Supplies, Vendor fees, etc. Typical time codes may include Meetings, R&D, Marketing, Training and Onboarding, PTO, Vacation, etc.

9. Does Celoxis support the Project Baseline?

   Yes. Exactly one baseline can be set per project, covering either the entire project, or selected tasks. You can then compare the moving project timeline with the previously set baseline. Since only one baseline exists per project, setting new baseline will override the existing one. Please refer to the Working with Baseline guide in our How-to series.

Conclusion/Final Points

The Celoxis functionality covered in this document are just some of the techniques you can use to your advantage when tracking budgets and costs of your projects. The cross-project reports representing multiple views and slices of your projects’ data can be created, configured and shared easily, forming an accurate at-a-glance view of individual accounts, project portfolios and the entire organization. The multiple input and output data points, including but not limited by those listed below can easily be represented in various reports and visual charts, placing all the crucial data at your fingertips. Just remember that even for the most comprehensive and sophisticated systems, the output data is going to be only as good as your inputs. Always encourage your team to track the required financial data accurately, and enter the time and expense information in a regularly and diligently manner. Then, just leave the rest to the system to supply you with the accurate real time project health representations.

Input fields by you

Some of the outputs that help tracking the projects’ and tasks’ health

Celoxis provides your organization with two flexible billing models: User based, and Time code based (also know as activity based billing), making it easy to track the billing amounts for different types of projects. Furthermore, Celoxis allows you to have the projects of Fixed price, as well as Hourly billing types, providing for both the flat fee and the time-and-material billing approaches. By following this simple how-to manual, you will be able to easily arrive to the estimated, and actual billing amounts for your invoices, regardless of the billing model your company follows. After studying this manual, you will learn about:

• Setting up the organization’s billing model
• Setting up project’s billing type
• Setting up bill rates
• Tracking actual and estimated billing amounts
• Valuable billing-related input and output metrics

Setting up your organization’s billing model

When setting up Celoxis for the first time, one of the major decisions that will affect every project in the system, is to adopt one of the two available billing models:

• User based
• Time code based

This is done on the Timesheet section of the Administration page. You must have the Administration rights to access these settings. Select the appropriate billing model to instantly affect the settings for the entire system.

In the User-based model, separate bill rates will be added for every billable user in the system. The rates then will be factored into the billing amounts for the projects, both actual and estimated.

To provide the default billing rate for a user, open the user’s settings and enter the desired hourly amount in the Bill field of the Default Rates ($/Hour) section in the Basic tab

For every user in the system you can have default/company billing rate which will automatically apply to every project. At the same time, you can override rates for any given user on any given project. See the Other scenarios, and frequently asked questions section for more information on this subject.

The billing amount for this model is calculated by multiplying the number of billable hours entered by each user into the timesheet of the project, by the billing rate of the user.

To provide the default billing rate for the time code, navigate to the Administration page (you must have the Admin privileges) and follow the Time Codes link in the Timesheet section. Enter the desired hourly rate amount into the Bill field. Note that the Bill field will only be available, if the company’s billing model is set to Time code based.

Setting up project’s billing type

Celoxis allows you the flexibility to specify Fixed Price or Hourly billing type for each project.

Setting up billing for the Fixed Price projects

In a Fixed Price billing type, the tasks you undertake and bill for, are for a fixed pre-defined price.

To set the project to the Fixed Price type, navigate to the Financials section of the Advanced tab in the Add/Edit Project dialogue. Note that the different billing models are only available to the client projects. For the projects where the client is not specified, the Billing Model field will stay hidden.

Selecting the Fixed Price option from the Billing Model dropdown, opens the new Fixed Price field, allowing you to enter the amount you are planning on invoicing.

When you opt for this type, the ‘billable’ option for expenses and time entries in the project is not checked, by default.

How rates work for Hourly projects

When you choose Hourly from the Billing Model dropdown, the billing amounts are calculated from the hours that the users log in their timesheets. The bill rate of each user is taken either from user’s settings or from the time code, depending upon the company's billing model.

When this billing type is used, the ‘Billable’ option for expenses and time entries in the project will be automatically checked, by default.

Tracking Actual Billing Amounts

With the billing rates set, the actual billable amount for each task is calculated using this formula, which takes in consideration both the labor and the material bills:

Amount (Act, Billable) of a task = Hours (Act, Billable) × Bill rate + Approved and Billable expenses on the task

Amount (Act, Billable) of the project is calculated from the sum of the amounts of the project’s top tasks. Depending upon the org billing model, the bill rates comes from either the user’s bill rate or from the time codes picked in the timesheet.

For example, if a resource working at the bill rate $30phr reported 10 billable hours for a task, and the project manager approves the $1000.00 billable material expense for the same task, the Amount (Act, Billable) for this task will be calculated as follows:

Amount (Act, Billable) = 10hrs × $30phr + $1000 = $1300.00

Celoxis provides another useful indicator that captures the estimated billable amount for all the labor effort on the project. Amount (Est, Billable) is calculated by using a similar formula, as the sum-product of user's bill rate and estimated hours on that task.

Amount (Est, Billable) of the project is calculated from the sum of the amounts of the project’s top tasks.

Note that the Amount (Est, Billable) is available and calculated only when the User based billing model is used. In addition, with the User based billing, if project's billing type is Fixed Price, the estimated billing for the project equals the set fixed price and therefore does not provide estimated billing values at the task level.

For Time code based billing, estimated billing cannot be calculated, thus the Amount (Est, Billable) column is not available.

Celoxis also lets you keep track of time entries and expenses that have been invoiced. The Invoice status of the items for any given task can be seen in the Task Details dialogue.

On the organization level, you can also create a cross-project report that shows per project:

• Amount (Expense, Invoiced)
• Amount (Time, Invoiced)
• Hours (Invoiced)

Manager and Executive Cross-Project Reports

Below are just few examples of the helpful and easy-to-generate reports which can additionally inform you about important billing metrics. Each report can be easily configured, grouped, ordered or turned to a visual chart to your liking.

Other scenarios, and frequently asked questions

1. What happens if I change the company’s billing model?

   This is a major step that may impact the running projects as well as the visible column of the financial reports. Please refer to the Switching between Billing Models article for the complete list of the potential ramifications.

2. Why are there the "None" options for the company’s and the projects’ billing models?

   The company billing model should be set to None if your organization does not do billing, or if for some reason you do not want to track your billing in Celoxis.
   Setting the billing type to None at the project level means that no billing is done for this particular project. This is helpful for internal project, proof of concepts, or pro bono initiatives.

3. We have different billing rates for certain projects. How can I achieve that?

   You can specify the project-specific billing rates for every user and for every project using More >> Billing Rate function. If the billing rate of the user is not specified for the project, it will default to the rate set in the Edit User dialogue.

4. What happens when there is a billing rate adjustment to the users with projects in progress?

   The actual billing amount for the work already performed will be calculated at the previous rate. The amount of all future work will be calculated using the new rate. If you have any saved entries, and the rate has changed before the entries were committed, the new rate will be used upon commit and approval of the entries.

5. What happens when there is a bill rate adjustment to the time codes with projects in progress?

   Similar to the users’ billing rates, the billing for the work already performed will be calculated at the previous rate. The billing of all future work (including any saved time entries) will be calculated using the new rate.

6. Why some of the time entries and expenses are automatically marked as Billable, while others are not?

   Whenever new time entries or expenses added to the projects, they can be marked as billable or non-billable. The project billing model determines the default behavior for the billable checkboxes.
   

   • Fixed Price model – billable is unchecked by default
   • Hourly model – billable is checked by default

   This default behavior takes in consideration that with the Hourly model, the hours must be tracked in order to generate the proper client invoices, while in the Fixed Price model the invoicing is based on the fixed price but is not affected by the actual efforts spent by the project resources.

7. My projects are fixed-price projects. How can I track milestone payments?

   Please refer to the detailed guide on Milestone-based Billing.

8. Do you provide integration with any accounting software?

   Yes, Celoxis has an out-of-the-box integration with QuickBooks Online for managing and recording invoices. Here’s the link to a short video.

Conclusion/Final Points

As with any type of data, the billing in Celoxis depends on the accuracy and thoroughness of the inputs provided by project managers, administrators and other users. Please make sure you take time discussing the parameters of Celoxis implementation before the system is deployed to the organization, to arrive to the most optimal billing model for your company. By the same token, please make sure your project managers are aware of the differences between the project billing model, and are using the correct model for every project. Finally, encourage your project managers to keep an eye on the users, and time codes’ billing rates, to guarantee that the accurate billing data exists across all projects in the system.

The following input and output fields exists in the out-of-the-box configuration of Celoxis to help with your day-to-date billing needs

Input fields by you

Some of the outputs that help with the projects’ billing

Celoxis is a very flexible platform and quickly adjusts to manage your scrum projects. In this document, we will show you how to setup your projects for Scrum. With Celoxis, you can quickly define and manage your product backlog as well as plan and run your sprints.

Managing the Product Backlog

1. Create your Scrum Project with a suitable name (AddProjectNew Project). Start: Date when your first sprint is scheduled to start Manager: Select a user who is the Product Owner/ Scrum Master. Client: Select the project’s client.
2. Now, create a task called “Product Backlog” which is a summary task. This is where the Product Owner will plan and manage backlog items for sprint planning.
3. For each user story, the Product Owner will create a task in the Product Backlog Project. The Product Owner will not define any resources or dates at this point. So leave the default dates as-is for every user story added.
4. The backlog should be groomed regularly by the Product Owner, stacking up the stories as per their priority and assigning relative size to them. To assign relative size to items (tasks), create a single select custom field “Story Points” using the famed Fibonacci series options. Attach this custom field to tasks and add the column to your Gantt.

Planning Sprints

1. Create your Sprint 1 task (From Gantt click AddTask).
   Each Sprint will be represented as a summary task in Celoxis.
2. Next, expand the Product Backlog and look for stories that the Product Owner, the Team and the Scrum Master think make sense to be done in this sprint. The selection should made based on the target velocity that the team decides for the sprints. Select user stories whose Story Points add up to this target velocity.
3. Move the selected user stories from the Product Backlog into your Sprint as subtasks under Sprint 1 (Summary Task)
4. Once the user stories are picked up for the Sprint, your team gets to decomposing them into smaller activities or subtasks.
5. For each of these activities, the team selects the appropriate dates and assigns resources and estimates the effort.
6. Once all stories are converted into tasks, review the sprint to make sure its duration adheres to the sprint iteration. Despite the fact that sprint’s Story Points hits the target velocity, some tasks or activities required to complete them may affect the fixed iterations. In this case, you will need to work with your team to reshuffle the work or remove one of the stories from the sprint (i.e. move it back to the Product Backlog)

Running Sprints

1. Once your sprint is loaded and your project is Active, your team can get the work done. Your team can also update the Status field which depicts the current status of the task in the sprint.
2. As they work through the items, they can fill Timesheets to log the actual hours spent on each task. Once these hours are approved by the Scrum Master, the system will automatically update the Remaining Work on the task.

Sprint Status Report

This is tabular report that gives you a real-time picture of all the stories in your current sprint.

The Line chart helps you to understand what is planned and actual efforts for specific period or sprints.

What you don’t get

Burn down charts - Currently, we do not have burn down charts. Our product and engineering teams are working to make this happen in Celoxis.

You can baseline a project and its tasks, and, in the future, compare actuals versus the baseline values to understand the deviation. Celoxis also supports Earned Value Analysis (EVA). In most scenarios, you would want to think of baseline as the "original estimate". In such cases, you would baseline the project just before kick-off. Celoxis currently supports only one baseline.

Creating a Baseline

Go to the project's gantt chart by clicking on Project ActionsGantt. Then click on ToolbarBaselineSetProject. At any point in time, you can also choose to add or reset baselines of selected tasks. For example, if the scope increased and new tasks were added, you can add only these new tasks to the baseline by selecting this tasks and clicking on ToolbarBaselineSetSelected Tasks.

The following fields are baselined:

• Planned Start
• Planned Finish
• Planned Effort
• Planned Cost
• Budget

Visualizing the Baseline

Go to the project's gantt chart by clicking on Project ActionsGantt. Then click on ToolbarBaselineView.

Reporting on Baselines

Once you baseline project, the entire Earned Value Analysis (EVA) attributes like BCWS, BCWP, EV, PV, CPI and SPI are available in project and task reports. If you would to know more about earned value analysis, please read our blog article.

There are many baseline related columns available in projects and tasks.

Over the course of normal business, projects need to be properly re-evaluated for appropriate reprioritization. Often, at executive management directive, managers need to address an incoming high priority project request drop into the mix of pre-existing projects. This guide addresses how to:

1. Assess the impact of a new project on the existing resource workload,
2. Identify under-utilized or free resources,
3. Replace resources on tasks,
4. Shift out certain tasks to level out the workload,
5. If needed, shift out a low priority project completely to a later date.

Assessing Impact of New Project on Existing Workload

1. Create a new project state, say Requests (AdministrationProject ManagementProject States). Keep this new state in “Planning” stage and disallow time. This helps keeping the new project requests separate from the regular projects.
2. Create a project for your new project request and keep it in “Requests” state (AddProjectNew Project). Enter the planned start date for this project.
3. From the project’s Interactive Gantt tab, define the WBS and resources. Since the project is in “Requests” state, it will not affect your existing workload.
4. Access the Resource Load (ViewResource Load). By default, this view will show you pre-existing planned and active projects.
5. Edit Filters and Add “Requests” to the Project State Filter. Click on Apply. Now, your resource load view will immediately show you the impact that any new project requests will have on the existing mix and workload.
6. Because of the new project request, the impact on the existing workload is high and a lot of resources are overallocated.
7. You can download this view (Select “PDF” option from the top right button group) and send this to your executives to show the direct impact of the new requests on the existing mix of projects.

Identify Under-utilized or Free Resources

From the same Resource Load View, you can easily identify the under-utilized or free resources. These are the resources that are color-coded as blue.

Replace Resources on Tasks

You can directly replace resources on problematic tasks (Mouseover the task in contention, and select the 3-line menuEdit Resources)

In the example below, you can Edit the “Survey commercial spaces” task and reassign it to Tanya who is relatively free in that period.

Shift out Tasks

There could be situations where free resources are not readily available. In such cases, you may need to shift out certain tasks that are of low priority and can be easily shifted out. To do this,

1. Mouse over the appropriate task.
2. Click on the 3-line menu.
3. Select Edit Task. Here you can change the task’s start date to a later one.

Shift out Low Priority Projects

If you still have a resourcing issue, change the start date of the other low priority projects so that all other tasks in those projects are rescheduled. To do this,

Yes, it is possible to add a secondary manager who can monitor the project.

To do so, click on a project to open its panel and then click Project ActionsMoreAccess Control. In the new pop-up, click on the user icon for Project Manager and then select the user(s) you wish to add as secondary managers.

These users will be visible on the project's panel page under the Overview tab.

The Filters set in the report controls what data you want to see in the reports.

So, to remove completed projects from your view, you need to edit the report and ad the Filter Schedule Status and check all the options in the drop-down except the Completed value. Save the report for the new filters to be applied.

If a task has child tasks, then it is called a summary task. Many attributes of summary tasks are rolled up from its child tasks. Some of the non trivial attributes are described below.

Start Date (planned/actual/projected)
It is the minimum of planned/actual/projected start date of its children.

Finish Date (planned/actual/projected)
It is the maximum of planned/actual/projected finish date of its children

Work (Effort)
It is the sum of work of its children.

Constraints
Constraints are not applicable for summary tasks.

Resource allocation
Resources assigned to a summary task will not be factored into the planned cost of the summary task, nor displayed on the resource load charts.

% Complete

% Complete = (W1×P1 + W2×P2 + ... + Wn×Pn) ÷ (W1 + W2 + ... + Wn)

For all

leaf-level descendants where

is the work and

is the % complete of its

descendant.

Predecessors
If a summary task has a predecessor, the system considers it to be equivalent to having that predecessor for all its children.

Auto/Manual Scheduling
Since the planned start and finish are calculated from its children, summary tasks are always considered to be auto scheduled.

Budget/Costs/Billing
It is the sum of the budget/costs/billing of its children.

Duration
It is the working time between the task's start and finish date as per the project's work calendar

A task's predecessors are tasks that affect its start or finish date.

In the Build farmhouse project, consider two tasks Buy land and Flatten land. You cannot start the land flattening process unless the land has been purchased. Hence, Buy land is a predecessor of Flatten land. Flatten land is called the successor of Buy land.

Once predecessors are entered, that task's start and finish dates are always kept up-to-date by the system when any of the predecessors are rescheduled. In the above example, if the finish date of the Buy land task is pushed ahead by 10 days, Celoxis will automatically push the start date of Flatten land by 10 days.

Types of predecessors

Lead Time

In some cases, when a task is nearing completion you may want to begin another task. For instance, 3 days prior to the construction of the walls of your home is completed, you may want to start selecting the color of the paint for the walls. So, for the

task you will select the

task as the predecessor and enter a lead time of 3 days. Lead time is specified as a negative number. E.g. -3d indicates a predecessor with 3 days lead time.

Lag Time

Sometimes a task cannot begin as soon as another task is completed. For example, once you paint the walls, it may take another 2 days for the paint to dry and only then you can begin furnishing the room. In this case, you would select the

as the predecessor of the

task and enter a lag of 2 days. Lag time is specified as a positive number. E.g. 4h indicates a predecessor with 4 hours lag time.

Setting predecessors

Predecessors can be set using the interactive gantt chart or from the add/edit task form. On the interactive gantt, you can set predecessors using:

• Drag-Drop: you can drag from the beginning or ending of a predecessor to the beginning or ending of a successor to create any of the four dependency types.
• Predecessor Column: you can enter the serial numbers of a tasks's predecessors separated by the semi-colon character. E.g. 2;3
• Successor Column: you can enter the serial numbers of a tasks's successors separated by the semi-colon character. E.g. 5;6
• Edit Task Screen: selecting a task and pressing the e key (or Right ClickEdit) will open the edit task form. You can edit the predecessors as described earlier.

Setting inter-project predecessors

Inter-project predecessors can only be entered from the add/edit task screen. Open the task form using Task ActionsEdit and go to the Predecessors tab. Add a row. First pick the project and then the task dropdown will be populated with tasks from that project.

Note that inter-project dependencies cannot be edited from predecessors and successors columns in interactive gantt.

Constraints are applied to your tasks to impose restrictions on the way the task's start and finish dates are calculated. Often, they represent real world conditions. Examples:

• The last date to submit a bid is 20th May 2018
• Application testing can begin only after the phone is available in the market on 1st October 2020

We recommend that you use MSO and MFO only when absolutely required as they cause the schedule to be unnecessarily inflexible.

Setting Task Constraints

Task constraints can be set directly from the constraint columns or from the add/edit task screen.

Milestones are major checkpoints in a project. They can indicate the completion of key project tasks, the commencement of a phase or conclusion of the plan. For example, in a software development project, Research Complete can be a milestone that indicates that all the research activities have been completed and the project is now ready to move to the next step of preparing a Requirements Specification document.

In Celoxis, milestones are tasks that have zero duration and represented by a diamond symbol (◆) in the gantt chart.

Creating milestones

From the Interactive Gantt, click Gantt ToolbarAddMilestone.

To convert an existing task into a milestone, set its duration as zero.

Recommendations

• Set predecessors to your milestones. Doing this will illustrate the impact to your milestones.
• Set deadline (FNLT) constraints on milestones only if necessary as it will make it difficult to flexibly re-plan activities around your milestone.
• Indent milestones so that they appear under the correct WBS element

Critical tasks are those tasks which if slipped, could cause delays in the project. The critical tasks can be thought of as the longest dependent sequence of activities in a project plan which must be completed on time for the project to complete on the planned finish date. Critical tasks are automatically calculated by the system and cannot be manually marked.

Read our blog article on critical path for an in-depth look on this topic.

Tasks that have MSO/MFO/SNLT/FNLT constraint are also marked critical and will appear on the critical path.

A task stops being critical when it's completed, because it can no longer affect the completion of successor tasks or the project finish date.

Viewing critical paths

You can view the critical path from the interactive gantt by clicking Gantt ToolbarCritical Path.

Monitoring critical tasks

Tasks can be filtered using the Critical filter. Using this, for example, you can create a pie chart of critical tasks divided by their RAG indicators. Critical is also available as reporting attribute for tasks.

The topic of RAG indicators has been covered in-depth in this article.

Duration

Duration is the working time between a task's start and finish dates. For manually scheduled tasks,the duration has no significance.

Effort

Effort is the total amount of time resources will spend working on the task. Read our blog article on duration vs effort.

For manually scheduled tasks, if:

• Allocation is in % – the total work of that task is calculated as the sum: working hours x % allocation for each resource assigned.
• Allocation is in hours – the total work of that task is simply the sum of the individual allocations.

Units

The total allocation (in %) for the task. If a task is allocated – Joe[100%] and Peter[50%], its allocation is 1.5.

Relationship between D, W and U

The relationship between duration, work and allocation units is critical in understanding automatic scheduling of tasks. It is explained in detail in our

.

Schedule is an important pillar of the project management triangle. Celoxis has a flexible and powerful scheduling engine to help you take control of your project schedule.

Task scheduling is the process of calculating the start and finish dates of tasks. In this chapter we will understand how this is done in Celoxis.

We have already seen how start and finish dates of a summary task are calculated from its children. We shall now see how to calculate the dates for leaf-level tasks.

Manually Scheduled Tasks

Manually scheduled tasks are those tasks that have the Manually Scheduled option set. Celoxis never modifies the start and finish dates of manually scheduled tasks. Its predecessors are treated as FYI only and does not affect the start or finish dates.

The only constraint is that if you assign a resource with non-zero allocation, the resource must have non-zero (any value) allocation between the start and finish date of the task

Automatically Scheduled Tasks

Tasks that are not manually scheduled are automatically scheduled. Celoxis always keeps automatically scheduled tasks up-to-date. When a predecessor is extended, when a resource vacation is added, etc. the task dates are kept in sync.

Factors that affect scheduling of an automatically scheduled task are:

• predecessors
• constraints
• effort
• allocation units
• resource work calendars
• default work calendar (if no resource is assigned yet)

Scheduling Logic:

1. First, the task's predecessors are scheduled. Now all predecessors have correct start and finish dates.
2. Based on the dependency types, lead and lag, the task's tentative start (or finish if SF or FF predecessors exist) date is calculated. If the task has dependencies on both its start and finish dates (e.g. when a task has both FS and FF predecessors), a date is chosen that satisfies both dependencies. The date can either be a start date or a finish date.
3. Next, based on the effort and resource work calendars (or the default work calendar if the task is unassigned), the end date (or start date, if the previous step resulted in a tentative finish date) is calculated. To do this, the scheduler simply tries to exhaust the effort as per the allocation and the date when the effort becomes zero is the new finish (or start) date.
4. Finally, constraints are applied. If this results in a change of start or finish, the new date is taken as a base and the complementary date is calculated in the same way as in the previous step.

The progress of a task is indicated by its % complete attribute. A value of 0% means that there has been no progress on the task while 100% means that the task has been completed. Celoxis rolls-up the percent completes of tasks to calculate the percent complete of the project.

% Complete Methods

There are three methods to update a task's % complete. They are described below with an example – assume that we have a task T with resources Joe assigned 40h and Peter assigned 10h to it.

Last % Entered

The % complete of a task is the last % complete entered for that task by any user. This supposes a working model where the the person updating the % complete knows the overall status of that task. In our case, if Joe updates the % complete of to 50% and then Peter updates the % complete to 25. The % complete of T will be 25%.

Weighted Average of % entered by each assigned resource

The % complete of a task will be calculated as a weighed average of the % completes entered by resources assigned to it. This supposes that when a resources enter % completes, they are indicating their how much of their work is complete, not the overall progress of the task. The % complete of the task is calculated as:

% Complete = (W1×P1 + W2×P2 + ... + Wn×Pn) ÷ (W1 + W2 + ... + Wn)

For all n assignees where Wi is the planned effort and Pi is the % complete of its ith assignee.

Let’s say Joe enters 50% while Peter enters 100%. The % complete of T will be: (50×40 + 100×10) ÷ (40 + 10) = 60%.

Auto-calculated from time logged against the task

In this model, users do not enter the % complete, rather it is calculated based on the time logged against the task. The formula is:

% complete = actual effort ÷ planned effort

Actual effort is the sum of all approved hours for that task.

A few things to note in this model:

• Users will not be shown the % complete field as that value is calculated.
• If time logged exceed the planned effort the % will show as 100%.
• Once a task starts and you think that the task's effort has been over or underestimated, you should decrease or increase the planned effort of the task. Otherwise the task may never show up as completed or may prematurely indicate as completed.

We recommend that this only be used in projects when the time logged will always match the planned effort. E.g. tasks such as “Do 20 hours of research”.

Specifying the % complete method

The default % complete method for tasks can be specified from the project add/edit screen's Advanced tab.

% Complete of Summary Tasks and Projects

% complete of summary tasks and projects is automatically calculated as a weighted average from its descendants as per the formula:

% Complete = (W1×P1 + W2×P2 + ... + Wn×Pn) ÷ (W1 + W2 + ... + Wn)

For all

leaf-level descendants where

is the work and

is the % complete of its

descendant. If a leaf-level task is unassigned, its duration (in hours) is used instead of its work in the calculation.

When you assign a resource to a task, Celoxis allows you to specify whether you want the resource to work full time (100%), half time (50%), any other fraction (e.g. 30%) or even a certain amount of hours (e.g. 20 hours).

Entering the correct allocation is important when you want to monitor resource workload. E.g. if Joe is scheduled to work 100% on task T1 from M-F and also 100% on task T2 in the same time period, the resource load chart will show Joe as overloaded that week. This is because the total effort expected by each task will be 40 i.e. a total of 80 but Joe works only 40 hours per week. If you intended that Joe work half the time on T1 and half the time on T2, then you should set Joe's allocation to 50% for both tasks.

If you want to ensure that your resources are optimally allocated, you should enter the correct estimations while allocating resources. Only then can the system show a true picture of the workload distribution.

In the following sections, let's assume that Mary works 36 hours per week, Monday through Friday as:

Allocation in percentage (%)

When you allocate a resource in % on a task, you tell Celoxis the fraction of time will that resource be dedicated on a task from his work hours.

For example, Mary works 8 hours per day and you allocate her 50% to a task, it means she will work 50% every day. Let's see how the system will allocate her the work per day:

Allocation in hours (h)

When you allocate a resource to work N hours on a task, it means that that resource will spend a total effort of N hours on that task from the task start to finish. N is proportionally distributed every day as per the resource’s working hours that day.

Let'see how the system would distribute her work if Mary was assigned 9h to a task that ran M-F:

On a task, you can either allocate resources in % or in hours but not both at the same time.

Assigning resources

There are many convenient ways of assigning, replacing or removing resources on tasks.

To assign resources on single task

On the interactive gantt, click on the resource cell -or- double click on the resources next to the task bar.

On the task overview or tasks list screens, Click on the icon that appear next to the resources.

From anywhere, click on Task ActionsEdit and click on Resources.

To assign resources on multiple tasks

On the interactive gantt, select the tasks and click Right MouseAssign Resources.

To replace or remove a resource on multiple tasks

On the interactive gantt, select the tasks and click Right MouseReplace a Resource. To remove, do not select anyone to replace the resource with.

When you create tasks from API, CSV Import or using the Add Multiple action from the gantt, you can create tasks by specifying or not specifying the start, finish and duration attributes. This chapter helps you understand how Celoxis sets the attributes that are unspecified.

In the following table, we shall use S for Start, F for Finish and D for Duration. The symbol manual is set to true if the creator has indicated his preference for creating manually scheduled tasks. Also, auto means that the system will use scheduling logic to calculate that attribute.

if (manual) { 
    S = max(today, project's start)
    F = S + 1d
} else {
    D = 1d
    S = auto
    F = auto
}

if (manual) {
  F = S + 1d
} else {
  D = 1d
  SNET = S
  F = auto
  S = auto
}

if (manual) {
  S = F - 1d
} else {
  D = 1d
  FNLT = F
  F = auto
  S = auto
}

  manual = false
  S = auto
  F = auto

  manual = true

  manual = false
  SNET = S
  S = auto
  F = auto

  manual = false
  FNLT = F
  S = auto
  F = auto

  manual = true

Also, if the task is deemded to be manually scheduled and if S and F were specified but without time i.e 00:00 hours, then S/F time will be set to the start/end working time on their respective weekdays. If that day is a non-working day, then most common start and end times during a work week will be used instead.

Celoxis can create tasks from emails sent to it. This is especially useful when you don’t have the application open in front of you or you are on the go.

Emails have to be sent to a specific address and be in a specific format. Task is created from the from, to, cc, subject, body, attachments and priority as described below.

To (special address)

The email address to which the email should be sent can be found under AdministrationProject ManagementTask Inbox. We recommend that you save it as a contact under "Celoxis Add Task” or something equivalent.

From

The user whose email address matches the from email address is considered to be the creator. This user must have Add TaskGranted in the project in which the task is to be created.

To and Cc

Users in Celoxis whose email address matches the email address of the email's recipients are assigned to the task with 100% allocation.

Subject

The subject should start with the name of the task followed key-value pairs of attributes encodes in square brackets. An example is shown below.

Add missing images in footer [project:Fifadom.com][parent:Images]

The above will add a task named “Add missing images in footer” in the project whose code or name is Fifadom.com under the summary task named “Images”.

Project is mandatory, rest all attributes are optional. Attributes supported in the subject are:

Body

The body of the email becomes the description of the task.

Attachments

All file attachments are attached to the task.

Priority

The value of the X-Priority header is checked to determine the task's priority. If it is 1 then the task's priority is consider High, if it is 5 then the priority is set to Low, otherwise it is set to Normal.

Celoxis provides you with the ability to import tasks in a project from CSV. If you have a Microsoft Excel file, then you can export it in CSV (comma separated values) format and then import it in Celoxis.

To import tasks in a project, first click on the project and then click Project ActionsMoreImport Tasks (CSV). Alternatively, if you are in the project Gantt chart, you can click AddImport CSV

Fields supported:

• WBS Code - using this you can create the WBS structure (parent-child relationships) for tasks after import. E.g. If we enter WBS codes as 1 for A, 1.1 for B, 1.2 for C and 1.1.1 for D, and 1.1.2 for E, and 2 for F then on import you will get:

     A
     ├── B
     │   ├── D
     │   └── E
     │
     └── C
     F

• Name - mandatory
• Description
• Planned Start - YYYY-MM-DD format
• Planned Finish - YYYY-MM-DD format
• Resources - enter resources in the format described here.
• Duration - enter in the duration format described here.
• Work - the effort in hours
• % Complete
• Budget
• Fixed Cost
• Planned Non-labor Cost
• External Key - the key or id of this task in another system e.g. JIRA
• Custom Fields - you will have to create the fields in Celoxis first

To read more about tasks dates,

.

Copying tasks copies task attribute, attached files and security while moving tasks also moves the attached entities like time logs, expenses and updates.

Copying or moving tasks in the same project

1. Open the project's interactive gantt chart
2. Select the tasks to copy or move
3. Press Ctrl+C to copy or Ctrl+X to cut
4. Select a task underwhich to copy/move these tasks and press Ctrl+V

Copying tasks from a different project

1. Open the project's interactive gantt chart in which you want to copy the tasks to
2. Click AddCopy from another project from the toolbar
3. Select a project and choose tasks to copy. If you choose a summary task, its descendants will also be copied.
4. Submit the form

A copy of the tasks will be created.

Moving tasks to a different project

1. Open the project's interactive gantt chart from which you want to move the tasks
2. Select the tasks to move
3. Right click and choose Move
4. Select the destrination project

Tasks will be moved to the new project. The rolled-up data of both, the new and old, projects are updated.

Celoxis makes it easy for users to indicate their progress on tasks. In addition to entering comments on a task from its task screen, you can:

• Update progress of many tasks in bulk.
• Update progress of a task via email.
• Update progress of a single task, which is the topic of this chapter.

Clicking on the for a task in a task list will open a menu having convenient options to update progress.

% and Comments

As you can see from the below image, you can log a custom % complete, enter comments and also log time. You can also enter actual start and actual finish dates if you wish, else the system will assume that the task started and finished on time.

In addition to logging an update using the web interface, task assignees can also reply via email to file their update. When managers request an update, assignees get an email like this:

Clicking on the Update Progress button as shown above, opens up a new email compose window in which you can modify the subject to fill in % complete, hours and time code. All are optional. You can also attach files and add a description that will become the progress update's text. A sample is shown below:

A few minutes after the email is sent, this progress update will be added to the task. If you have put in hours, time will also be logged and sent for approval.

You can create copies of a task in a recurring pattern of you choice.

1. Open the interactive gantt in the project in which you want to create the recurring task.
2. Create a task and name it appropriately e.g. Weekly Meeting.
3. Right click on the task and click on Recur.
4. Enter the desired recurrence pattern. In the following example, we have chosen a weekly pattern.
5. Submit

Celoxis will create new tasks as per your recurrence pattern as shown below:

You can request an update on tasks from their assignees. There are two ways to do this: for a single task, click Task ActionsRequest an Update, while for multiple tasks you can use the bulk actions.

Assignees get an email to which they can simply reply to to record their update. They can also specify the % complete, log time and more as described in this chapter.

You can attach one or more files to a task from your local drive or from Google drive. Click on the task to open the slide panel and then click on Attach Files. Files attached to a task can be viewed from the Files tab on the slide panel.

If you follow a task, you will be notified about activities happening on the task e.g. when someone adds a comment or when someone attaches a file. The notifications will be through email as well as through the notification center. If you are an assignee or a project manager, then you are automatically notified and there is no need to explicitly follow the task.

Unfollowing

To unfollow a task, simply click on the Unfollow link on the task screen on in the footer of the email notification.

You can select multiple tasks and perform actions on them. Click on the next to the checkbox in the report table header as shown below:

50%, 100% & On Track

Updates the % complete of selected tasks. For "On Track", read this.

Request an Update

Sends an email to the assigned resources asking them for a progress update.

Edit

Allows multiple attributes to be modified at once, including custom fields as shown below:

Gantt in Celoxis provides a graphical overview of the project schedule. This is useful for the Project Manager to schedule his projects and keep track of them. The different features like the Export, Baseline, etc. help him with preparing and driving the project plan more efficiently.

The Gantt chart features include:

• Creating the WBS i.e your tasks, sub-tasks, milestones with start and finish dates
• Drag - Drop tasks to re-order them in hierarchy
• Add Constraints
• Drag - drop-dependencies
• Expand-collapse the task list
• Assign users on tasks
• Updating task progress
• Printing the Gantt
• View the schedule with different Zoom levels
• Auto Save and Manual Save options

Configuring the Gantt

The first time you access the Interactive Gantt of a project, you are presented with the below options to be configured. This is then remembered per person across all projects in Celoxis as a user preference. You can change this setting from the icon.

Keyboard Shortcuts

The scheduling mode of a task is determined from the Gantt preference which is saved per user. However, you can change the scheduling mode of one or more tasks from the Gantt. To do so, select the tasks and click on MoreSet Scheduling Mode to the desired one from the Gantt.

Yes, you can create a report of tyep Task and the Output type as Gantt. On the Report's edit page, under the Visible to Client drop-down pick the client whith whom you wish to share.

This report will then appear under the Reports menu for the client.

Once you add the dependecy, it will be shown as below:

For more details, refer the Setting inter-project predecessors section here.

A time entry in Celoxis passes through various states as shown below.

Saved

Saved indicates that the time entry has been saved but not submitted for approval.

• Anyone with add time privilege can create a time entry in this state.

Pending Approval

Pending approval indicates that the time entry has been submitted for approval.

• Anyone with add time privilege can create a time entry in this state.
• The submitter can continue to edit time entries in this state.

Approved

Approved indicates that the time entry has been approved by

approvers setup in your approval workflow.

• Anyone part of the approval workflow can approve time.
• Once approved, that time entry cannot be edited by the submitter. However, anyone with the Approve privilege can make changes to the time entry.
• Information from approved time entries like hours, cost and revenue are rolled-up to their respective work items and projects.
• During approval, the time entry is updated with the latest bill and cost rate.

Rejected

Rejected indicates that the time entry has been rejected by

approver.

• Anyone part of the approval workflow can reject time.
• The submitter is notified through an email.
• The time entry will start showing in the weekly timesheet screen of the submitter where it can be edited or deleted and can be resubmitted for approval.
• A rejected time entry resubmitted for approval has to go through the entire approval workflow.

Invoiced

Invoiced indicates that the time entry has been marked as invoiced.

• Only time entries marked as Billable can be invoiced.
• Anyone with Invoice privilege can invoice a time entry.
• Once invoiced, the time entry’s invoiced hours and revenue are rolled-up to their respective work items and projects. E.g. invoiced revenue and invoiced hours.

A time code represents an activity type for a time entry. For example, a software development company may want to track acitivities like Programming, Designing and Testing, while a legal firm may want to track activities like Litigation, Research, Meetings, etc.

Time codes help in:

• Filtering: you can filter time entries based on activities and perform bulk actions on them.
• Reporting: you can aggregate information about your activities and create pie, bar and various other types of reports. For example, software development companies can understand the total time spent in Programming or Designing.
• Billing: if your organization uses activity based billing i.e. the billing rate is based on the activity performed not who performs it, then you can define billingrates for time codes. When time is logged, the appropriate bill rate gets applied to that time entry based on it's time code to calculate its bill amount.

Non-project time codes

Some activities are not associated with projects yet that time has to be accounted for. E.g. Meetings, Sick Leave, and Paid Vacation. This can be done using non-project time codes. A non-project time code is like a regular time code but with its

flag turned on.

Using time codes

Time codes are selected by the submitter while logging time. Time codes can be selected on the weekly time screen or while logging time on work items.

Managing time codes

Only administrators can manage time codes. Navigate to AdministrationTimesheetTime Codes.

Costable

Every time code has a costable flag. When time is logged, if it's time code is costable, then the time entry is marked as costable. Costable time entries are considered towards project cost. Most of your time codes will be costable, however, some could be non-costable e.g. Unpaid Vacation and Unpaid Sick Leave.

In addition to tracking hours, timesheets are also used in calculating labor costs and for billing clients.

Labor Cost

All costs associated with time entries are labor costs since they are directly associated with human labor. Whether a time entry is considered towards project cost depends on its Costable flag. By default this is set based on whether its time code is costable or not. But this can be changed by a user having the Approve Time privilege.

Cost Rates

If time entry is marked as costable, its cost rate is the cost rate of the time entry's owner. If the owner's cost rate has been specifically set for that project, it is used. Otherwise, that resource's default cost rate is used.

If time entry is not marked as costable, its cost rate is set to zero.

Setting the default cost rate

A user's default cost rate can be set from its add/edit screen or from the bulk edit user screen.

Setting a project specific cost rate

You can override the default cost rate for users per project. Click on a project link that will slide in the project screen; then click Project ToolbarMoreCost Rates.

Setting cost rates for a specific time entries

Users having the Approve Time privilege can edit a time entry (or many using the bulk edit time screen) and set a cost rate.

Billing

Whether a time entry is considered for billing depends on its Billable flag. By default this turned on if its work item's Billing Type is set to Time & Material. But this can be changed by a user having the Approve Time privilege. Note that changing the billing type of a work item will only affect its future time entries.

Celoxis supports two types of billing models:

• Time code based — This is when you bill your clients based on the activity performed, not on who performs that activity. For example, a software development may decide to charge a rate of $50 per hour for a junior Java developer; it does not matter which exact user does that work. In this case bill rates are defined per time code.
• User based — This is when the bill rate depends on the user performing the activity. For example, in a legal firm a star lawyer may charge twice the rate for the same kind of work. In this mode, bill rates are defined per user.

Your organization can have only one model at a time and administrators can select it from AdministrationTimesheetBilling.

Overriding rates for a project

Like cost rates, billing rates can also be overriden per project. Click on a project link that will slide in the project screen; then click Project ToolbarMoreBill Rates.

Setting bill rates for a specific time entries

Users having the Approve Time privilege can edit a time entry (or many using the bulk edit time screen) and set a bill rate.

You can setup a multi-level approval workflow for time entries. For a time entry to be marked as approved, it has to be approved by all the approvers. If any of the approver rejects it, the time entry is sent back to the submitter. On resubmission, the entire approval workflow is started.

For time on projects

For non-project time

Changing the workflow will result in resetting the approval status of all items that are pending approval. They will have to start from the first approval.

You can use timers in Celoxis to keep track of time spent on your work items. Timers can be used in tasks as well as your custom apps.

Timers can be started on work items using the icon in the toolbar as shown below. Once a timer is started, it automatically pauses the earlier running timer. Also, you can use the icon to pause a timer from a work item.

Once a timer is started, it is shown in the toolbar in green color. You can click on it to view all you recent timers. This is also a convenient way to pause a timer or restart a new one.

To fill your weekly timesheet, click Main MenuAddTimesheet. The weekly timesheet screen is a quick, powerful and convenient way to log time as well as update task progress.

You can click Save to save the timesheet or Submit to save as well as submit the timesheet for approval.

You will need the Time & Expense > ApproveGranted privilege to approve time-entries. To approve time-entries, click on Main MenuApprove Time.

The above example shows time-enntries submitted by Tanya and Joe Cool. You can check the boxes besides the users and then click Approve to approve all time-entries in one click OR click Timesheet to open Timesheet view to see the individual time-entries before approving.

The Incomplete Timesheets report helps you identify and remind users who have not filled their timesheets.

To view incomplete timesheets, click Main MenuReportsIncomplete Timesheets.

Customizing the definition of "Incomplete"

If you click on Edit Filters above, you can customize the value of the Hours (Submitted) filter. You have two options:

• Less than working hours – If Joe is supposed to work 40 hours per week and a non-working exception of 4 hours has been added, then Joe is supposed to log 36 hours of time. Anything below this will be treated as an incomplete timesheet.
• Less than N hours – You can decide the N and all uses who have logged time less than this value will be shown.

Setup daily timesheet reminders

If you have administrator privileges, you can set this up from AdministrationTimesheetTimesheet Options. Check the Send incomplete timesheet reminder emails to users daily at option and select the time you want the emails to be sent and click on Save. The time selected is as per your company’s time zone.

By marking time entries as invoiced, you are indicating that the client has been sent an official invoice from your company. You will need the Time & Expense > InvoiceGranted privilege to mark time as invoiced. To mark time as invoiced, click on Main MenuInvoice Time. This will show a list of all billable time entries that have been approved but not invoiced.

You can select multiple time entries and perform actions on them. In any time log report, Click on the next to the checkbox in the report table header as shown below:

To perform an action, you will need the appropriate privilege. Also, time entry has to be in the correct state as per the workflow. So if you try to invoice an unapproved entry the action will fail.

Edit

You can set individual attributes of time entries or update the bill and cost rates to the latest values. The latter is especially useful when you have modified the rates and you need to update time entries with the new ones.

This article helps you understand how you can manage overtime hours and arrive at project costs and billing using the time codes in Celoxis.

Steps

1. Define additional Project Time codes for each of your overtime activities and mark them as costable. For example, if you have existing time codes as Research, Design, Development, then create additional overtime time codes such as Research (OT), Design (OT), Development (OT).
2. Define regular cost and bill (if user-based billing) rates for your users.
3. In case of Time code based billing, also define the overtime bill rates for your overtime time codes.
4. Create a ‘Time Entry’ report with below details,
   Name: Overtime Entries Select a filter ‘Time Code’ and select all overtime time codes in this filter Select a filter ‘User’ and mark it as promptable Output: Tabular. Select the columns as Date, Hours, Cost Rate, Bill Rate Group By: User, Time Code
5. When users want to log overtime hours, ask them to select appropriate overtime time code in the timesheet.
6. When approving time entries, filter the report (created in step 4) based on a specific user E.g. User: Joe Cool. This will display all the overtime entries by Joe Cool.
7. Now select all the overtime entries and click on bulk edit action.
8. In case of time code based billing model, select Cost Rate option, and set the overtime cost rate.
9. In case of User based billing, select the Cost Rate and Bill Rate options and then set the overtime cost rate and bill rate.
10. Approve the time entries.

Sample Reports

1. Regular vs Overtime (Tabular Report)

   

2. Overtime Distribution (Pie Chart Report)

   

Yes, Celoxis allows you to apply the new rates for time-entries already submitted or approved. When the time-entry is saved or submitted for approval, the new rates are automatically updated during approvals.

However, once a time-entry is approved, you need to consciously edit them to apply the new ratesusing the bulk actions.

For steps, refer here.

An expense in Celoxis passes through various states as shown below.

Pending Approval

Pending approval indicates that the expense has been submitted for approval.

• Anyone with Add Expense privilege can create an expense in this state.

Approved

Approved indicates that the expense has been approved by the project manager.

• Once approved, that expense cannot be edited by the submitter. However, anyone with the Approve privilege can make changes to the expense.
• Information from approved expense like cost and revenue are rolled-up to their respective work items and projects.

Rejected

Rejected indicates that the expense has been rejected by the project manager.

• The submitter is notified through an email.

Invoiced

Invoiced indicates that the expense has been marked as invoiced.

• Only expense marked as Billable can be invoiced.
• Anyone with Invoice privilege can invoice an expense.
• Once invoiced, the expense’s invoiced revenue are rolled-up to their respective work items and projects.

An expense code represents an expense type for an expene line item. Some common expense codes are Meals, Gas, Phone, etc.

Expense codes help in reporting. You can aggregate information about your activities and create pie, bar and various other types of reports. For example, you can understand how money is being spent across various avenues.

Using expense codes

Expense codes are selected by the submitter for each line item. You can use expense codes in filters, output columns and even charts.

Managing expense codes

Only administrators can manage expense codes. Navigate to AdministrationExpensesExpense Codes.

The submitter of an expense can mark it as billable and costable. If an expense is marked as billable, its total amount is added to the work item's and consequently its project's revenue. If the expense is marked as costable, its total amount is added to the work item's and consequently its project's cost.

Expenses can be added against tasks. Each expense can have multiple line items. Each line item can be assigned an expense code like Travel, Food etc.

To add an expense, click Main MenuAddExpense. Alternatively, you can also click on a task and from the task screen click Task ActionsMoreAdd Expense.

You will need the Time & Expense > ApproveGranted privilege to approve expenses. To approve expenses, click on Main MenuApprove Expenses.

The above example shows two expenses submitted by Tanya. You can click on an expense to approve or reject them individually OR select one or more expenses and click on One Click Approve to approve them in bulk..

By marking expenses as invoiced, you are indicating that the client has been sent an official invoice from your company. You will need the Time & Expense > InvoiceGranted privilege to invoice expenses. To invoice expenses, click on Main MenuInvoice Expenses. This will show a list of all billable expenses that have been approved but not invoiced.

Yes, you can edit the approved expenses if you have the requisite privileges. You need to have Time & Expense > EditGranted and Time & Expense > ApproveGranted privileges to be able to do this.

The notification center is used to communicate events and messages about items you are interested in. Events could include that someone completed a task in your project, or you received a new reply to an online discussion, or a new version of the file you are interested in is available, etc. The following image shows 2 new notifications and 1 new mention.

In-App Notifications

In-app notifications are events that happen in items that you follow, manage or own. The include new work assignments, modification to items, updates on tasks, replies in online discussions, etc. The number of unread notifications appear above the icon. You can click the icon anytime to view your recent notifications.

Clicking on any item in the panel will open that items's panel while clicking on Mark All Read will mark all unread notifications as read.

@ Mentions

@mentions is the best way to grab your colleague's attention to a work item. You can mention a user while:

• Adding a comment on a task or updating its progress.
• Performing an action, reassigning or adding a comment to an app item.
• Participating in discussions.

The number of unread messages appear above the

icon. You can click the icon anytime to view recent messages directed at you.

Clicking on any item in the panel will open that items's panel while clicking on Mark All Read will mark all unread messages as read.

Mentioning a User

The easiest way to mention a user is to click the icon in the text field's menu as shown below. Also, if easier, you can simply type @<first-name>, @<last-name>, @<username> or @<first-name><last-name> in the text field. In the following example, Emily and Tanya will see this message in their mentions when they login.

At times, you need to track updates on work items where you are not assigned but are related to the work you're doing. By following a work item:

• You get updates via email notifications about the updated on the work items.
• You can even reply to the emails, which will then add your comments against that work item.

Following a work item is a great way to stay up-to-date with its updates and comments. When you follow a work item, you see its updates in the Activity Stream and receive instant email notifications.

Follow a Work item

Assignees of a task or app item and the State Manager/Project Manager automatically follow that task or app item. To begin following a work item:

• Click on Follow link on the panel of the task/app item.
• Alternatively, go to the task or app item's actions menu and click Follow.

The Activity Stream report allows you to view the recent happenings on projects, tasks, bugs, etc. that you are assigned to, manage or follow. This report can also be placed on one of your dashboards. An example is shown below:

As you can see the history is grouped by each object and the recent happenings for that object are shown. You can click on View All to view all activities since that object's creation. There is also a comment area where you can put in your comment. And like any other report, you can customize what you wish to see.

Files often go through an evolutionary process and undergo a series of revisions. In teams, a file often involves contributions by different people. Without some kind of control, some important questions become difficult to answer:

• Do I have the latest version of the file?
• Am I overwriting someone else's changes to this file?
• Who all are working on this file?
• What changes were made since the last version that we sent to the customer?

Using Celoxis, you can answer these and many other questions. Celoxis offers a basic version control system that is simple, intuitive and user-friendly.

Basics

Files in project and task folders can be version controlled. The basic process is:

• Check-out a file
• Make changes on your local computer
• Check-in a file

Check-out

Checking out a file indicates to the system and your team that you intend to make modifications to that file. After check-out, you can keep this copy on your personal computer, make changes to it and then check it back in.

Multiple users can check-out a file at the same time except if a check-out has been marked as exclusive mode. An exclusive check-out means that no one else can perform a check-out on that file until you check it in or revert your check-out.

If someone else checks in a file while you are working on it you will be notified. For instance, if you have a version 1.3 of a file and some one checks in a version 1.4, you will be notified that you have an older version.

To check-out a file

Click File ActionsCheckout.

To undo a check-out

If you have checked out a file but decided that you do not need to update it, you can revert the check-in by clicking File ActionsRevert

Viewing current check-outs

If you select the versions column, or on the document info screen, you can see the list of users who have checked the file out. An X indicates that the check-out is exclusive.

Check-in

Once you are done with your changes to the file on your computer, you must perform a check-in for your team to see it. When you check-in a file, you have to upload the new version of the file and enter your comments. The system maintains a history of all check-ins.

Celoxis also warns you of potential conflicts. For instance, consider the following scenario:

• You checked out version 1.0 of a file on Monday in a non-exclusive mode because you want to add a few chapters.
• Joe checks out the same version i.e 1.0 on Tuesday to correct a few spelling mistakes.
• After correcting typos, Joe immediately checks it back in to create version 1.1. Now these corrections obviously don't show up in your file since you have an earlier copy. At this point, Celoxis will send you an email notification indicating that a new version of the file is available indicating that your version is possibly outdated.
• If you try to check-in your file, Celoxis will warn you that there was a checkin on the same file while you were making your changes and hence a potential for conflict. After this warning, you will need to merge the changes (e.g. using Microsoft Word's merge feature) and check the file back in.

To check-in a file

Click File ActionsCheck-in. You have the choice of indicating it as either major change (e.g. 1.2 → 2.0) or a minor change (1.2 → 1.3). Version numbers do not affect system behavior and can be used as per your business policies. A best practice is to indicate a check-in as major when you intend to send it to your client.

Revision history

To view all the revisions along with the comments, click File ActionsView Details. You can also download a specific version of the file.

When you add calendar events, you can indicate the impact it has on resource availability. For example, if you are going to an off-site meeting for a day, you would not want any tasks to be scheduled for you that day.

When you add calendar events, you can indicate the impact on availability in the following ways:

• No – this event has no impact on availability
• Yes, Working – will add the event duration to the availability of the owner as well as all invitees who have accepted the invitation.
• Yes, Non-Working – will remove the event duration from the availability of the owner as well as all invitees who have accepted the invitation.

Sharing controls how others see your calendar. If you mark your event's sharing as:

• Private — The event is not visible to any user other than yourself and invitees.
• Show as busy —The event is shown as 'Busy' and no details are shown other than to you and the invitees.
• Public — The event is shown to everyone.

You and your team can conduct discussions in a project. You can also decide to involve the project clients in the discussion. An example where a team discusses the about a design is shown below.

Initiating a Discussion

To start a discussion, click Main MenuAddDiscussion. Alternatively, you can also click on a project to open its panel and then click Project Actions ▸ More ▸ Start a discussion.

Managing Participants

Participants can view the discussion and also get email notfications of all replies. They can simply reply to the email and even add attachments and the discussion will be automatically updated.

To manage participants click on Edit button. You can change the followers or decide whether to give access to the project's clients from this form as shown below.

Closing a discussion for comments

If you close a discussion for comments, no more posts will be allowed in it. To close, click on Edit button and check the Close this discussion for comments as shown in the image above. You uncheck this option at any time in the future.

Celoxis sends email notifications on work items when you are either assigned to or manage a work item. You are also sent email notifications when you follow work items.

In either case, you can reply to these emails to record your comments. If you attach files in your email reply, they will be attached to the work items.

Unsubscribing from email notifications

If you are a follower and want to stop receiving email notifications, you can unfollow that work item by clicking on the Unfollow link in the email footer. If you are not a follower but are assigned to or manage the work item, you can adjust your email preferences.

Attaching files to projects

For details click here.

Attaching files to tasks

For details click here.

Attaching files to custom app items

For details click here.

Like adding files, you can also add links to folders by clicking on the icon for the folder and clicking Add Link.

Every project has its own folder by default. In most cases, you will be uploading files to this folder. If you have a lot of documents, you can create sub-folders in this folder. The following example shows that the project has two sub-folders Home Page Samples and Logos.

To add a sub-folder, click on a project to open its panel and then click on the Files tab. From the menu besides the project name folder, click on Add Subfolder as shown above.

As the project progresses, you might realize that the scope of the document or the documents in a folder is for another project or was simply attached to the wrong project or task.

In such situation, you can move the file/folder to the correct project/task using the Move option available under the Document actionsMoreMove of the document.

To view all the revisions along with the comments, click File Actions ▸ View Details. You can also download a specific version of the file. The following image shows the version history. Clicking on the version number will download that version of the file.

You can add events in your calendar and if you have administrative privileges, you can also add events for other users, for a work calendar or for the entire company.

To add an event, click on the icon on top-right and then double-click in the date cell on which you wish to add the event.

Follow the steps below to export the Celoxis Calendar to Outlook.

• Get the URL of the Celoxis Calendar.
• Copy the link.
• Now, go to the Calendar in your Outlook application.
• Click on Open Calendar > From Internet.

Yes, clients can participate in discussions once they are added to it as Followers. For more on Followers, refer here.

You can view calendar of other users. Events marked as "Public" by that user are shown and you can view details of the events. Events marked as "Busy" will show as "Busy" for the duration of the event. "Private" events are not shown.

To view them, click on the Users drop-down and select the user whose events you wish to see.

Yes, the document content is searched. Your search results will have the name of the document if any matching keywords are found.

In a Document report, there is a filter Attached To which helps you filter documents that are attached to a project or task.

Yes, you can share a documnet with a client. When upload documents, you will see a checkbox Share with client which once checked, will show the document in a document report shared with a client.

Custom Apps are powerful workflow-driven applications built by customers like you. You can define the steps, people involved at each step, capture custom fields and even define time-out rules. All this with our super powerful reporting capabilities makes Custom Apps a great complementary tool to the rich project management capabilities in Celoxis.

Customers are using custom apps to manage leave approvals, client change requests, equipment quality checks, software bugs, and many more! If you are using spreadsheets to maintain something, think about moving to Custom Apps.

The power of custom apps is best illustrated by a scenario. Acme Consulting has created a bug tracking application in Celoxis.

1. Acme's customer sends an email to bugs@acme.com with an image as a file attachment.

2. The bug is automatically created in Celoxis along with the image as its attachment.

3. Quentin, from the QA team, starts seeing the bug in the Unverified Bugs pane on his dashboard.

4. He verifies that it is indeed a bug and marks the bug as Verified.

5. The bug is automatically routed to Dave, a software developer.

6. Dave is notified via email and also sees the bug in the Bugs assigned to me pane on his dashboard.

7. Dave fixes the bug and marks the bug as Resolved. While doing this, as per the company's policy, he also enters the list of files modified in a custom field.

8. The bug is automatically assigned to the same user who verified the bug (Quentin) to test.

9. The company policy is to test all bugs within 72 hours but Quentin misses it.

10. An email is automatically sent to the QA manager and Quentin about the lapse and the bug is marked as delayed.

11. Quentin verifies the fix and marks the bug as Closed.

12. An email is automatically sent to the customer about the fix.

13. Customer likes Acme.

As you can see Celoxis created the bug from email, then routed it to the right people, and as they completed their bit of the work, captured necessary information from them before moving it to the next person’s bucket, and at the same time keeping a watch for any delays.

We shall learn about building custom apps through an example. We will build a simple bug tracking application. We shall assume we have two teams: Developers - they fix bugs, and QA (short for Quality Assurance) - they test the fixes by developers. We will to the model the following bug workflow:

In plain english, the diagram translates to:

• When a bug is reported, it is in the New state.
• QA verifies the bug. If it is not a bug, the bug moves to Closed; else to the Verified state.
• A verified bug fixed by a developer moves to the Fixed state.
• The fix is then tested by QA and the bug moves to Reopened, if test fails; or Closed, if the test passes.
• A Reopened bug fixed by the developer moves to the Fixed state.

Each bubble is represents a stage in the bug life-cycle while each arrow an end-user action. Next to each state we have defined the team responsible for it. Also, note that there is no way for a bug to move from any state directly to any other state e.g. A bug cannot move directly from

to

We, ourselves use our own bug tracking application but we have a lot more states to indicate whether a test case was present, if documentation was updated, if a test case was added, etc. Similarly you can make the workflow as complex or simple as you like. But for now, let's stick to the simple workflow that we discussed above.

Creating an App

To create an app, go to AdministrationAppsApps and click on

. You will see a form with many tabs. We will cover each tab below.

The Basic tab

This tab defines some basic properties of the app. In addition, it also controls certain behaviours of the app.

The States tab

This tab defines the states of the app. You can also mark the start and end states in the workflow. We have listed all the states in our bug workflow.

The Workflow tab

This tab defines all the

in the workflow diagram. Each arrow represents an end-user action. We shall see more about its usage later on in the documentation.

The Triggers tab

.

In our bug tracking app, we don't need any triggers. However, let's take this help desk workflow for example. In case of the help desk app, the requestor will be the person who asked a question. When that person replies via email, we would want the ticket to be automatically moved to the Unresolved state as then it would be brought to the attention of the support team. In other words, we would want the Reopen transitions to happen. In this case, we would be defining our triggers like this:

The State Managers tab

A state managers is a user who is treated as a Manager when an app is in a particular state. They are notified when things happen to an item in this state. In our example below, Mark is the QA manager, so he is responsible for the New and Fixed states where the QA team is supposed to do work. You can override state managers at a project level if the person managing that state is different.

What's Next?

We have created a custom app for our bug workflow. In the next chapter we will be adding some custom fields to the bug.

In the previous chapter, we created the workflow, here we create custom fields for our bug. By default, all workflows have the following fields:

• Name
• Priority
• Assigned To
• Requestor
• Due Date - an optional date indicating when the estimated completion date of this item
• Description

Let's add a few fields to our

:

• Affected Versions - a list of all versions affected by this bug
• Fixed Versions - a list of all versions in which this bug fix has been uploaded

Since we want the

field to be available while creating a bug, we attach it our

app. Since we want the developer to enter the

field

when he is marking the bugs as fixed i.e. Verified → Fixed and Reopened → Fixed, we attach it to the

actions as shown below:

What's Next?

We have created our application and also defined custom fields for it. In the next chapter, we will see our bug tracker in action.

Till now, we have been configuring our application. It's time we understand how your users will use the app. We will see how our app has affected the user interface and also walk you through a real-world scenario.

Bug app and the user interface

Add menu

appears as an option in the Main MenuAdd menu.

View menu

also appears as an option in the Main MenuView menu.

New Report menu

You will also be able to create a report for the

app. The entire arsenal of filters, groups, charts, etc. is available at your disposal.

Adding Bug

Megan wants to report a bug. She clicks Main MenuAddBug and she sees the form: In addition to the regular fields, you can see the custom fields we added earlier.

Bug in state: New

The bug has been assigned to Quentin, our QA guy. He clicks on the bug link and sees:

Performing the Verify action

Quentin verifies the bug indeed exists and clicks on

. He is presented a form like this:

He assigns it to Vardhan, a developer. He also has the choice of notifying Megan, who has opened the bug. But since there is nothing noteworthy to report, he decides against it. After he submits the form the Bug moves to the Verified state.

Bug in state: Verified

Vardhan receives an email notification about his being assigned to this verified bug. He clicks on the link and sees the following:

Performing the Verify action

Vardhan fixes the bug and clicks on the

button. He is presented a form like this:

Notice how he is presented with the Fixed Versions custom field.

What's Next?

The example above demonstrates how the bug moves across states, how the right fields are captured at the right time and when notifications are sent. It should give you a good idea about the capabilities and advantages offered by Celoxis custom apps. We have also seen that there is an option to send emails to requestors. Celoxis allows customizations of these emails and that is the topic of the next chapter.

In the last chapter, we have seen that you can notify the requestor while performing actions. In this chapter, we will understand how to control the email format using simple templates. It is important to understand that these templates only control the emails sent to requestors not the other notification emails that are sent to users.

Customizing the email template

Open AdministrationCustom AppsRequestor Email Templates. You can customize the global template or customie the template per workspace. Click on the icon next to

workspace to edit the global template.

.

What's Next?

In this chapter we have seen how to configure the emails that are sent out to requestors. In the next chapter, we will see how to add time-based rules to our app.

Timeout policy is a set of rules that define what should happen when an app item exceeds its stay in a particular state for more then the specified hours.

In the earlier chapters, we created the workflow and also defined our custom fields. Now, we will add in some timeout rules.

Continuing with our Bug app, let's assume that our company is a strict on QA and mandates the following:

• Rule #1 A new bug should be verified within 48 hours. If it is a high priority bug, then it should be verified within 24 hours instead.
• Rule #2 A bug that has been marked fixed should be tested within 72 hours after the bug is marked fixed. If it is a high priority bug, then it should be tested within 48 hours instead.

Adding a Timeout Policy

Open the app list screen by going to AdministrationCustom AppsApps and clicking on the icon for our Bug app. Then click on the Add button.

What's Next?

In this chapter we have seen how to define timeout policies and what they are used for. In the next chapter, we will see how to initiate workflows from emails.

Custom Apps can be initiated by emails. Emails can either be free form (sent by people) or structured (generated by filling a web form).

Direct Interface

This is used when we want to start workflows when people and send an email to a particular address. For example, we may want to create bugs when our cutomers send an email to bugs@acme.com.

For more information visit the AdministrationCustom AppsEmail Integration page.

Indirect Interface

This helps you integrate an existing system with one of your custom apps. For example you have a web based form on your web site that users fill and submit to initiate an workflow in Celoxis.

In this model, your program will send a plaintext email to an email address with a well formatted body as described in AdministrationCustom AppsEmail Integration page.

Email Aliases

When you want to use the direct email interface, you would want to expose nice and simple email addresses to your users. For example, bugs@acme.com or support@weyland-yutani.com. However, addresses generated by Celoxis are like abracadbra+NEI-4.g0.1b.2m8.0.0-eqro@celoxis.com. The way to bride the two is through email aliase.

Let's say that Acme wants create bugs in Celoxis when people send emails to bugs@acme.com. Acme would:

1. Generate the email address for the bug by going to: AdministrationCustom AppsEmail Integration. Let's say that this email address is gobbledygook@celoxis.com
2. Acme in it's email server would create an alias that would redirect bugs@acme.com to gobbledygook@celoxis.com
3. If Acme is a SaaS customer, they would notify us of this mapping and we would update our servers. This typically would take one business day.
   If Acme is an On-Premise customer, they can open Site AdministrationSite SettingsEmail Aliases and enter bugs@acme.com:gobbledygook@celoxis.com in the text area, save and restart the server.

When working on an app item, the assignee or the manager at times might need to record comments on it.

To add comments, click on the app item for e.g your bug, risk, etc. On the panel of the item, click on MoreComments. You can check the Notify Requestor checkbox if you wish to notify the requestor of the app item about this comment.

Once the comment is added, all the followers receive an email notification with the new comments.

To attach files to a custom app item, click on the item and on its panel click Attach Files as shown below.

If you follow an app item (e.g. a bug), you will be notified about activities happening on it e.g. when someone adds a comment or when someone attaches a file. The notifications will be through email as well as through the notificiation center. If you are an assignee, project manager, or a state manager, then you are automatically notified and there is no need to explicitly follow the task.

Unfollowing

To unfollow, simply click on the Unfollow link on the item's Overview tab on in the footer of the email notification.

At times, you may want to re-assign the bug, issue to another user due to several reasons like the assigned user is on leave or is busy with other activities.

To reassign an app item, click on the app item for e.g your bug, risk, etc. On the panel of the item, click on MoreReassign. The new user will get an email notification about the new assignment.

You can move an app item to another project or workspace. To do so, click on the app item for e.g your bug, risk, etc. On the panel of the item, click on MoreMove. You will be prompted to select the project or Workspace to which you wish to move the app item.

Celoxis provides you with the ability to import app items (your bugs, risks, etc) in a project from CSV. If you have a Microsoft Excel file, then you can export it in CSV (comma separated values) format and then import it in Celoxis.

To import app items in a project, first click on the project and then click Project ActionsMoreImport Apps (CSV). For simplicity, we strongly recommend that you import one custom app at a time. So instead of having one file items.csv, you should split that into multiple files like bugs.csv, risks.csv, issues.csv and import them one at a time.

Fields supported:

• App – Mandatory field. The app name (e.g. Bug, Risk).
• Name – Mandatory field. A short description.
• Description
• State – This should be one of the states you defined for your app. If not present will be defaulted to the first state in the app definition.
• Due Date – YYYY-MM-DD format
• Assigned To – The name, username or email address of the user to whom the item is to be assigned.
• Requestor – The name, username or email address of the requestor whose account is in Celoxis.
• Requestor Email (External) – The email address of the requestor who does not have an account in Celoxis.
• Requestor Name (External) – The name of the requestor who does not have an account in Celoxis.
• Custom Fields – one column per custom field of the app

Allows multiple attributes to be modified at once, including custom fields as shown below:

Yes, using the Direct or Indirect email integration, your clients can initiate app items via email.

For more details, refer

.

When defining your custom app, there is a check box Clients can initiate this app which you can uncheck so that your clients do not initiate this.

There are many entities in Celoxis like projects, tasks and time logs. Some entities are also created by you using custom apps like bugs, risks, and issues. Each entity has its own attributes as well as attributes aggregated from other entities contained in it. For example, the project entity has its own attributes like name, priority, manager as well as attributes approved hours, invoiced revenue, planned labor cost, actual labor cost, etc. that are calculated from other entities like tasks, time logs and expenses.

When you create a report on Celoxis you have to first pick an entity on which to report. You can choose from:

Time Phased

Time phased reports show how a quantity is distributed over time. For example, when you run a project report, you can see the total estimated cost of the project but if you want to understand the planned spend per week or month, then you will need to run a time phased report. Many quantities has time phased nature. E.g. budget, hours allocated to resources, cost, revenue, etc.

You can view time phased data in a tabular format as shown below or in the form of charts. Currently, unlike other entities, charts are not drill-down capable.

Filtering allows you to exclude unwanted data in your reports. Celoxis provides comprehensive and powerful filters for a large number of attributes including your custom fields.

Setting filters

A report's filters can be changed from the add/edit report screen. A sample screen with multiple filters including a custom field (Module) is shown below.

When multiple filters are selected, row have to match all filters. If a filter has multiple values (e.g. Module), then the row has to match at least one of those values. If you create a report with the above filters, then only those rows will be returned where (Display Tasks is in In Progress) AND (Module is one of UI or Middleware) AND (Planned Finish is in This Month) etc.

Running User filter

In the above example, you can see the the assignee is set to the special value of - Running User -. This indicates that the assignee must be filtered based on the person who is running the report. E.g. when Joe runs this report, he will only see his tasks while when Mary runs the same report, she will see her tasks.

Running User's Subordinates filter

This option is available in most user filters. The user should be a subordinate, directly or indirectly, of the person running the report. This option is useful when a manager wants to keep track of activities of his/her reportees. For example, if Joe wants to monitor all the high priority tasks assigned to his team, he should create a report, set the priority filter to High and Very High, and set the resources filter to - Running User's Subordinates -.

Prompt filters

In many cases, you would want the end-user to change the values of some of the filters. In the above example, the report allows the end-user to change the values of Display Tasks, Module and Planned Finish at the time the report is run. The below diagram shows how a user running the above report can modify the filters:

In the above example, the user has changed the Planned Finish filter from This Month to Last Month and also cleared the Module filter.

The kind of display you want can be selected from the Output tab on the add/edit report screen.

Tabular

This is the default output type and presents the data in a tabular output.

The view is quite dynamic with multi-level grouping and sorting, group totals, grand totals, etc.

This view is highly personalizable - you can change columns, grouping and sorting to suit your needs. See the top right hand side of the image above.

This view also has great productivity boosters. You can do bulk actions, perform an action on a line item by clicking the icon and even edit an attribute right there by clicking on the icon.

Show Totals Only

Show the total rows only. If the option was checked in the above report. You would only see the group and grant total rows and not the individual project rows.

Hierarchical

This organizes the row as per the parent-child relationship. It is only available for task, file and client reports. View this example that shows tasks grouped by project with the hierarchical option checked.

When this option is checked, the resulting totals only include those objects that result from the filters not the objects included (even if they don't match the filters) to show the hierarchy.

Gantt

The Gantt output is available only for project and task reports. In case of tasks, the output is a cross-project gantt chart as shown below.

Calendar

The Calendar output generates a calendar view for projects and tasks as shown below. The bar is colored as per the color of the project or task. You also have the option of turning off the bars in which case the start and finish evernt for the task and project will be separately generated.

Pie Chart

It is easy to create pie charts in Celoxis. These settings were used to create the Pie chart below.

Bar Chart

Celoxis supports a number of popular bar chart formats. Each of the bar chart type has been explained below and the form settings used to generate the chart has also been provided.

Simple Bar

The following bar chart was generated using these settings. Note how the Sort By setting sorts the bars in decreasing order. If you set the Bar Orientation as horizontal, it would result in this chart.

Comparison Bar

The following comparison bar chart was generated using these settings.

Stacked Bar

The following stacked bar chart was generated using these settings. Notice how the colors correspond to the color of the health indicator.

You also have the option of stacking it side-by-side.

Bubble Chart

The following bubble chart was generated using these settings.

If you do not select the bubble size, then this will become a scatter chart and all bubbles will be of the same size.

Card View

Card view is available as an output type for projects, tasks and apps. You can also drag and drop card across lanes if the lane's attribute is user-editable. For example, you can drag and drop if the lane was a custom field like Kanban Status but not if the lane was system calculated field like Schedule Health.

Administrators can schedule reports to be emailed to specific users at regular intervals. To schedule a report, open the edit report screen and then click on the Schedule tab. You will see something like:

In the above example, the report will be run with the running user as Megan every Monday (since 12th Aug 2018 is a Monday) at 1:00 AM and the resulting PDF will be emailed to Weyland and Yutani.

Only non-virtual users can be selected as the report subscribers

Reports can be shared with your team or with clients.

Sharing with users

Sharing with users is determined by the Visible to Users field on the Details tab on the add/edit report screen.

• To keep a report private, do not share it with anyone.
• To share it with specified workspaces, select those workspaces.
• To share it with everyone in your company, choose -All-

.

Sharing with clients

Sharing with clients is determined by the Visible to Clients field on the Details tab on the add/edit report screen.

• To keep a report hidden from clients, do not share it with anyone.
• To share it with specified clients, select those clients.
• To share it with all clients, choose -All-

.

The tabs that you see on the project screen are also reports.

Your account comes with some default tabs but your administrator can customize them to suit your organization. Open AdministrationProject ManagementProject Views and you can add, edit, delete, and reorder the reports. A sample of the project views management screen is show below. Note now the order of the reports corresponds to the order of the project tabs.

Dashboards are one of the most important screens in Celoxis. Not just for the information they can convey but also for the amount of things you can get done right from your dashboard.

A dashboard is a collection of reports. You can create different dashboards for different roles and functions. For example, you can create a task and project monitoring dashboard as well as the popular RAID logs dashboard for your project managers.

You can also create dashboards for clients. Client can get a nice overview of their projects, track their change requests, approvals, etc., and keep tabs on their online discussions.

An example:

Creating Dashboards

Celoxis allows shared dashboards as well as private dashboards. To create a dashboard choose Dashboard from the Main MenuReportsAll ReportsNew Report menu. An example: In the above example, we are creating a dashboard that is:

• Named: Sample Dashboard
• Shared with all users
• Shared with clients: Client1 and Client 2
• LHS is 65% wide (implies RHS is 35% wide)
• The first column has three reports: Upcoming Milestones, Task Status and Risks

Filters

The dashboard filters allow data of only those projects that match the filter criteria. Marking filters as Prompt enable the person running the report to change its values.

Shared Dashboards

To create shared dashboards you will need the Add ReportGranted privilege. This can be set from the AdministrationAccountAccess Control screen. To maintain control, we recommend that you give this privilege only to responsible users.

Personal Dashboards

Personal dashboards are dashboards that are only visible to their creators. Personal dashboards can be created by users who do not have the privilege. To allow creation of personal dashboards, check the Allow Personal Dashboards option from AdministrationAccountCompany Information screen.

Assigning Dashboards to Users & Clients

Dashboards can be assigned to users and clients from their add/edit screen's Preferences tab. You can assign multiple dashboards and reorder them too. The first dashboard becomes the default dashboard for that user. Let's see the dashboard selection for Joe: From the above image we can see that Joe has been assigned three dashboards: Tracker Board - that lists out status of projects and tasks, RAID log - that tracks Risks, Issues, etc. and Weekly Status - that allows him to track the weekly updates.

If Joe, after logging in, clicks on Dashboard in the main menu, he would see something like:

Assigning dashboards similar to another user or client

Using the bulk edit screen's Dashboard Like... field, you can set the dashboard of multiple people to be like a particular person. For example, you can select Mark, Peter and Luke and make their dashboards exactly like Xavier.

Limits

Please read the Limits chapter for more information.

Fetching and processing large amount of data not only slows down your response times but also for other users. We have put reasonable limits on the amount of data required to generate reports. If you are an On-Premise customer, you can change these limits but we strongly recommend that you do it after much deliberation.

Report Limits

15,000 records

For any report to run, it performs database queries. If a query returns more than 15,000 rows, the report does not run and an error message is shown to the user.

To remedy this problem, you should add more filters, especially those filters that can be performed in the database query itself. The most common filters are date filters since most likely you are interested in recent data. Project state filter, task completed filter and time entry state filter are also some useful filters that you should consider in limiting data.

Duration in Time Phased reports

Time phased reports are resource intensive as they perform a lot of dynamic calculations. The Period filter selects the duration of the report and is limited as follows:

• If zoom level is Day the period cannot exceed 3 months.
• If zoom level is Week or Month the period cannot exceed 12 months.

Dashboard Limits

A dashboard is a collection of reports. It is equivalent to running all the reports at once. Naturally, to control performance, we have to put some additional limitations on dashboards.

A dashboard has the following limits:

• Time phased reports, Gantt rendering and Incomplete timesheet reports are not allowed on dashboards. You can star them for quick access.
• A dashboard can have a maximum of 6 individual reports.
• The maximum number of shared dashboards in an organization is 10.

To create reports, you must have the Reports > AddGranted privilege. To add a report, open the reports' panel by clicking Main MenuReportsAll Reports and then click the New Report button. Then pick an appropriate report type. This will open a form, details of which are explained below:

Details

• Visible to Users — The group of users this report should be visible to. Read More.
• Visible to Clients — The group of clients this report should be visible to. Read More.

Filters

The filters to limit the data for this report. Read More.

Output

The display you would like for this report - pie chart, bar chart, tabular, etc. Read More.

Schedule

Whether you would like Celoxis to email this report at regular intervals. Read More.

To get quick access to reports, you must star it. Starred reports appear in the Main MenuReports menu. Some reports, because of performance reasons, cannot be put on dashboards. If you use them regularly, then it will be a good idea to star them so that you can access them in a couple of clicks.

To star or unstar a report, first run that report and then click on the or icon in the report title. In the above example, the report is already starred as indicated by the filled star prefixed in the report title.

You can download a report by clicking on the button. Reports can be exported in the following formats:

• PDF – in A4 format
• CSV – all records in the report are exported but there is no grouping of data
• CSV (Grouped) – all records in the report are exported and grouped as you see in your browser

Virtual users are like regular users except they don't have logins and hence cannot login to Celoxis. Virtual users are free. Some use-cases are non-human resources like machinery, conference rooms and computers. Virtual users can also be used in instances where you want to assign tasks to that person but do not want to give access to the system. E.g. consultants.

Using Virtual Users

Virtual users:

• can be assigned to tasks
• receive related email notifications - task, discussions, etc if their account has an email address is specified.
• can themselves update progress and log time on their tasks via email. Read more.
• can participate in discussions via email
• can add comments to app items via email

Creating virtual Users

A virtual user is created in the same way as a regular user except that the Virtual User option is turned on.

You can create your organizational chart in Celoxis using Reporting Managers. The main advantages of creating your organizational structure are:

• Reporting managers have automatic visibility into their reportee's work.
• Reporting managers can be used in the time approval workflow.

Setting Reporting Managers

Since Reporting Manager is an attribute of the user, only administrators can change it. The field can be changed from the add/edit user screen in the Basic tab.

Administrators can add users. If you have a large number of users, you should consider importing users from CSV.

To add one user at a time:

1. Click Main MenuAddUserNew User
2. Select an appropriate user and click Next
3. In the Basic tab:
   1. Fill in Name, Email, Work Calendar, and Reporting Manager.
   2. If you wish the user to have a login, enter login and password, else click on Virtual checkbox
   3. Assign appropriate roles
4. In the Custom Fields tab, fill in the appropriate custom fields.
5. The Preferences tab will be prefilled based on the user we selected in the 2nd step. Read more about this tab.
6. Check the Add Another check box if you wish to add more users like this one
7. Submit

If the user was created with a login, an email with login information will be sent to that person.

You can change your language, formats, dashboards and customize email notifications from your preferences screen.

Changing Photo and Preferences

Clicking on the user icon in the main menu as show below: To change your photo, click Change below the photo.
To change your preferences, click My Settings

Preferences

Locale

Locale is a combination of language and country and determines the application interface language and number format settings. For example, choosing French (France), will not only change your application interface labels to French but the decimal point would become the comma symbol as expected in France.

Date Formats

The input date format is the format in which you will input dates in Celoxis. E.g. In the U.S., people prefer MM/DD/YYYY while in India, the preference is for DD/MM/YYYY.

The display date format is the format you wish to view dates when they are displayed.

Dashboards

You can choose the dashboards that appear in the main menu. The first one becomes your default dashboard. Read the chapter on dashboards for more information on dashboards.

Email Notifications

Celoxis provides you with the ability to import users from CSV. If you have a Microsoft Excel file, then you can export it in CSV (comma separated values) format and then import it in Celoxis.

To import users, go to the users page – Main MenuViewUsers and then click on the Import button. Upload the users in the format described below and in the Create users whose dashboard, preferences and security is like... choose the appropriate user. It may be required that you split your CSV file into different files so that you can import users with similar behaviours together.

Fields supported:

• Name - mandatory
• Email
• Phone
• Manager - the name or email of the reporting manager. This user must already exist in Celoxis.
• Username - the login name. Not applicable when SSO is in live mode.
• Password - the plain text password. Not applicable when SSO is in live mode.
• Virtual - true or false to indicate whether the user is virtual or not. If you specify this value as false or blank, then you must provide a username and a password for this user.
• Administrator - true or false to indicate whether to give this user admin privileges.
• Primary Job Role - the name of the job role.
• Custom Fields - you will have to create the fields in Celoxis first

On a successful import, all non-virtual users i.e users who can login are sent a welcome email with their login information.

When you no longer want a user to appear in pick lists, e.g. when a user leaves the organization, you should deactivate that user. After deactivation, that user will not be able to login and will stop appearing in any user pickers. If the user had a login, then it frees up a license that can be used for another user.

Celoxis does not provide a delete user because a lot of data, e.g. projects, tasks, discussion posts, time logs, expenses, updates and comments, is associated with a user and needs to be preserved.

Only administrators can deactivate users. To deactivate:

1. Click Main MenuViewUsers
2. Click on that user
3. From the user's actions, click Deactivate
4. If you wish to reassign the user's current responsibilities to someone else, select that user. If you select a user, then the following responsibilities will be reassigned to that user:
   • Open projects where the user is the project manager
   • Incomplete tasks assigned to the user
   • State Manager in various custom apps
   • Open custom app items
5. Deactivate

.

Celoxis lets you login as another user if you have administrator privileges. Logging in as another user is useful in many scenarios – to check if the dashboard is looking as expected, to change a setting that the user is having difficulty with, or to see what the user at the end of the telephone is looking at while he/she is describing the problem to you.

To login

Navigate to Main MenuViewUsers and click on for the user you wish to login as. Then click Login As from the menu.

To logout

Once you are done, you can click on Main MenuSwitch Back to logout as that user and automatically login as yourself.

Bulk actions allow you to select one or more users from a list view and perform actions on them.

Resend Login Info

Emails login information to the selected users. Emails are sent only to non-virtual users since only they have login access. Also, since Celoxis doesn't store the pasword, no password is sent; but a convenient link to reset the password will be sent in the email instead.

Bulk Edit

You can select one or more fields, including custom fields, of the selected users. Some interesting fields are:

• Dashboard like – sets the dashboards of the selected users to be like this one.
• Change Roles – replaces all existing roles of selected users with the ones chosen here.
• Bill & Cost Rates – sets the default rates for the selected users. Note that no time logs are updated. Task estimated costs are recalculated.

Yes, you can override the rates at project level. For details, refer:

and

.

The primary purpose of workspaces is to achieve flexible isolation of projects. Teams should be able to work independently without the possibility of stepping on each other but can work together if required. Consider the following real-world scenario:

Acme wants its engineering and marketing teams to work in isolation but for some marketing projects the marketing team should be able to bring in a few engineers on their project team. Acme also want a few people from the finance team access financials of projects from all departments. Plus, CXOs should have access to all projects in all departments.

Celoxis handles the above and many other real-world scenarios.

You can think of workspace as a department. In some cases, you can even map workspaces to geographical branches. It all dependens on how you want to segregate your projects and teams.

Managing Workspaces

Only administrators can manage workspaces. To manage workspaces, go to AdministrationAccountWorkspaces.

A privilege is like a permission. In Celoxis, if you want to view an item like project or task or perform any action on it like edit or delete, you will need the corresponding privilege. E.g. to view a task, you will need the Task > ViewGranted privilege, to delete a project, you will need the Project > DeleteGranted, while for logging time for another user you will need the Time ProxyGranted privilege. If you do not have the privilege, you will not be allowed to perform the action.

Celoxis has a very granular privilege structure — with over 50 privileges, you get fine-grained control over user actions.

Some actions like creating users, require administrative privileges. Any user can be given admin privileges. To do that, login as admin, edit the user and check the Administrator Privilege under Access Control. Users with the administrator privilege can peform any action even if they have not been granted privileges explicitly.

Privileges are assigned to roles. Read the next chapter to understand the interplay between privileges, roles and users.

Not to be confused with a job role, a security role is a collection of privileges. For example, we can create a Project Viewer role having the privileges: View ProjectGranted, View TaskGranted, and View FinancialsDenied. We can also create another role Project Collaborator with New DiscussionGranted and Add DocumentGranted privileges.

Role Based Access Control (RBAC)

Role based access control is an approach where access to an object for a user is controlled based on the roles the users is playing in that object. In this approach instead of directly assigning privileges to users, privileges are assigned to roles and roles, in turn, are assigned to users.

Why RBAC?

Why not just assign privileges to users? Wouldn’t that be easier? For teams with less than 10 users, the way of assigning privileges indirectly through security roles (RBAC) is probably an overkill. But as the number of permissions increase (Celoxis has around 60) and team sizes increase, managing privileges becomes difficult, error-prone and time consuming. When new employees are added to the team, the administrator will have to spend a lot of time giving them privileges and at the same time ensuring none of them are accidentally given (or denied) a privilege not intended for them.

With roles based security, admins would simply assign the new employee the right roles in the right workspaces. E.g. when Mark Marketer joins the company, all the admin would have to do is assign him the Junior Marketing Executive security role in the Marketing workspace. Mark is just another junior marketing executive whose security role has been carefully populated with the right access control privileges.

Managing Roles

Only administrators can manage roles in Celoxis. To manage, click AdministrationAccountAccess Control.

Users can play different roles in different workspaces. They can also play different roles in different projects.

Assigning Roles in Workspaces

Security roles can be assigned to users per workspace.

For example, Joe Doe, Vice President (Engineering), may be assigned the Project Supervisor role in Engineering so that he can perform any of the project actions in Engineering, assigned the Project Viewer role in Marketing so that he can view any project in Marketing, but play no role in Sales.

In Celoxis, you can assign security roles to users on the add/edit user screen or using the bulk user edit screen.

Assigning Roles in Projects

Users can be assigned roles in specific projects.

Users who play roles in a workspace, play those roles in all projects in that workspace. However, in some instances, you may want to give some additional privileges to a user in a specific project.

For example, Earl Engineer plays the role Project Viewer in the Engineering workspace. However, he is playing a lead part in one of the projects, so the project manager could give him the Project Supervisor role for that specific project. This would mean that Earl gets all the privileges associated with Project Viewer as well as Project Supervisor in that project.

Auto-Assigned Roles

Some security roles are automatically assigned to user, by the system, depending on the object on which the user is trying to perform the action on.

For example, if Mark, a project manager of a project, is trying to view a task in that project, the system will automatically assign him the role Project Manager only for that action. If Mark tries to view a task in another project of which he is not the project manager, he will not be assigned that role.

The following roles are automatically assigned to a user:

• Project Manager — when the user is a project manager of the object's project.
• Project Team — when the user is a project team member of the object's project.
• Task Team — when the user is trying to perform an action on a task assigned to him/her.

Auto-assignd roles make it convenient to define polices like "All project team members can view and comment on any tasks in their projects" and "Project managers should be able to modify any task in their projects" easier.

The Staff Role

If the user is performing any role in a workspace, then that user also plays the Staff role in that workspace.

The Staff role is a convenience that allows definiting policies for All members of a workspace. E.g. if you want all users in Marketing workspace to be able to view its projects, you would give the View ProjectGranted privilege to the Staff role.

How access control is checked is best explained through an example. Let's assume that Joe is attempting to edit the task T. The steps Celoxis would follow to determine if Joe can do this are:

1. Check for the administrative privilege

   If Joe has administrative privilege, then he will be granted the privilege. No other check is required.

2. Determine the privilege required

   Joe would require the Edit TaskGranted privilege on T

3. Check if the project can be viewed

   Since T belongs to a project, the system will check if Joe has the View ProjectGranted on T's project. If no, Joe will be denied the Edit Task privilege.

4. Gather all security roles played by the user

   The system will build a set of all roles that Joe plays in T. This would include :

   • All roles assigned to Joe in the project's workspace.
   • All roles assigned to Joe in the project.
   • Auto-assigned roles to Joe for the project and T.

5. Build the set of all privileges

   Since a security role is a collection of privileges, based on all the roles played by Joe, the system would build a set of all the privileges for all the roles played by Joe collected in the previous step.

6. Check if the privilege has been unanimously granted

   If the collection of privileges includes Edit TaskGranted and does not include Edit TaskDenied, then Joe will be granted the permission to edit the task T; else the permission will be denied.

You can assign roles to users in workspaces if you have administrative privileges. To assign roles, open the add/edit user form and select all the workspace::role combinations. In the following example, Janet is playing the role Developer in the Engr workspace. - All - :: <Role> is a shortcut to specify the same role in all workspaces. In this case, the CEO will most likely be assigned the role - All :: Executive. You can read more about this topic in this chapter.

You can make a user play some more roles in a project. Click on the project and click Project ActionsMoreAccess Control. This will open a screen like this:

Click on the icon next to the role and select the users who will play that role in the project. You can read more about this topic in this chapter

It is sometimes desirable to grant (or deny) additional privileges to roles for a specific project. To do this, click on the project and then click Project ActionsMoreAccess Control. This will open a screen like the one below.

The faded check marks indicate that those privileges have been assigned to roles at a global level. These cannot be changed. However, we can assign additional privileges to roles for which the privilege was left unspecified. We have done this for the Staff role for this project. We have allowed everyone playing the Staff role to view the project as well as to add tasks to this project.

Remember that in Celoxis, users can see or do things only if they have the privilege required to perform the action. Celoxis provides the View Financials and Edit Financials privileges to control view and edit access to financial information. Users can view financial information only if they have the View FinancialsGranted. E.g. if Joe is assigned a role that has been granted this privilege, only then Joe will be able to view the financial information.

If certain roles have been granted the View Financials privilege and you wish to revoke it, then you can do so from the access control screen.

In the unlikely scenario that you do not wish to show a user the financials for a specific project, then:

• Create a role say Financials Denied
• Assign it View FinancialsDenied.
• Assign the user this role for that project.

When a project is being planned, more often than not, we do not know the exact resource who will be working on a task. However, we know the job role or job function for that task. For example, we may know that to complete a task we need a Java developer but we do not know, or care, at that point who out of our hundred Java developers is going to work on that task.

Celoxis allows you to create job roles and assign them to tasks.

Using job roles has the following benefits:

• They act as a placeholder for a real resource — You can use the replace multiple resources functionality later to replace them with a real resource. Read more.
• They help in determining budget — When you assign a cost rate for a job role, it is used in calculating the estimated cost of a project
• They help in determining potential revenue — When you assign a bill rate for a job role, it is used in calculating the estimated revenue of the project.
• They help in understanding the demand and capacity gap — Their availability in Time Phased reports is always considered zero. Hence if you group by Job Roles, you can easily see the demand-capacity gap. This helps PMOs in determining which projects to accept and also make hiring decisions.

Using Job Roles

Job roles can be assigned to tasks. They are also available in columns and filters. You can aggregate information on job roles in reports and charts.

Capacity Planning

Job Roles play an important role in capacity planning and demand management. We have already bundled a capacity reports, that shows the net resource capacity in the future. You can customize this report to suit your needs.

Managing Job Roles

Job Roles can be managed only by administrators. To manage go to AdministrationAccount ManagementJob Roles.

Custom fields allow capture of business specific information on projects, tasks, users, clients and custom apps.

You can create custom fields of the following type:

Managing custom fields

Only administrators can manage custom fields. To manage, go to AdministrationAccountCustom Fields.

Reordering custom fields

You can control the order of custom fields in forms and overview screens. To reorder, open the custom fields screen as indicated above and click on the Reorder button. You can reorder the fields using -drag-n-drop.

Attaching custom fields to entities

Celoxis allows a custom field to be attached to various entities. For example, you can create a custom field Country and attach it to projects, users and clients without having to create a new field for each of them.

Customizing fields based on project types

If you want to capture different fields for different project types, select the appropriate project types for each field in the Attached To tab on the add/edit custom field screen.

Financial fields

If your intend to put sensitive financial information in your custom field, e.g. Target Profit Margin, check the Requires financial privilege option on the custom field add/edit screen. Users will require the View Financials privilege to view and Edit Financials privilege to edit the field.

Rollup fields

Sometimes it is required for task fields to be rolled-up to the summary task or project level. E.g. if you capture cable length used field for a task, then you would probably want to see the total cable length used at a project level. Marking a field a as a roll-up field allows this capability. You can roll-up the sum, average, min or max of a field.

To make a field rollup its value, choose the Rollup Method option to one of sum, average, min or max, on the add/edit custom field screen.

Colors

You can define colors for single-select and formula fields. If those fields have colors, the resulting value is formatted to show color. The color is also used in charts.

To define colors for a single-select field, define a color for each option. To define colors for a formula field, define a color for each possible output. To see the allowed values, click on the icon.

Formula fields

This topic has been covered in-depth its own chapter.

A formula custom field's value is automatically calculated by Celoxis based on its formula. The value is calculated every time the field is rendered. The formula expression language is sophistacted so you can peform complex data manipulations including arithmetic, string and date transformations.

Syntax

Celoxis treats anything between

and

as expressions. Formulas can be either defined as pure expressions e.g.

, or contain a mix of text and expressions as

when anything enclosed in

and

is treated as an expression and evaluated, while everything outside it is copied to the output verbatim as is. For the curious, if the formulae were attached to a project whose name was

and budget was

the output would be

and

respectively.

The dot operator

The dot operator is used to reference a property of an object. In the example

, the

refers to the project's budget if the custom field is attached to a project. The dot operator can also be used to call a function (a.k.a. method) of an object. In the example

, the

is a function call that would transform the project's name to upper case charcters.

Operators

• Arithmetic: +, - (binary), *, / and div, % and mod, - (unary)
• String Concatenation: +=
• Logical: and, &&, or, ||, not, !
• Relational: ==, eq, !=, ne, <, lt, >, gt, <=, ge, >=, le. Comparisons can be made against other values or against Boolean, string, integer, or floating-point literals.
• Empty: The empty operator is a prefix operation that can be used to determine whether a value is null or empty.
• Conditional: A ? B : C. Evaluate B or C, depending on the result of the evaluation of A.
• Assignment: =
• Semicolon: ;

The precedence of operators highest to lowest, left to right is as follows:

• [] .
• () (used to change the precedence of operators)
• - (unary) not ! empty
• * / div % mod
• + - (binary)
• +=
• < > <= >= lt gt le ge
• == != eq ne
• && and
• || or
• ? :
• =
• ;

Reserved Words

The following words are reserved for the EL and should not be used as identifiers:

Basic Examples

Utility Functions

The following set of helper functions have been provided:

Writing multi-line formulas

To write the formula code on multiple line, use the = and ; operators. The return value is the last statement of the formula. For example:

${
apc = entity.actualPercentComplete;
ppc = entity.plannedPercentComplete;
(apc - ppc)/ppc
}

The formula return data type

While defining a formula, you have to select a Formula Data Type. This tells the system what it should expect the formula to return. Celoxis formats the return value automatically based on the data type. For example, if you indicate the return type to be a currency, then if your formula returns a number 10000, the output would be $10,000 i.e. Celoxis automatically formats the number and prefixed it with the company's currency symbol.

The entity object

The entity object in formula represents the entity for which the formula is being evaluated. E.g. let's say that our formula field Client Advance is defined as ${entity.budget * 0.1} i.e it represents 10% of the budget. If we have attached this field to both projects and tasks, then while evaluating the formula for a project, the entity object would be a project while for a task it would be a task object.

Field reference

To view the list of available fields, click on the Field Reference tab on the add/edit custom field screen. Click on the plus icon to expand the list of available variables for the various entities.

Error handling

When there is an error evaluating a formula, e.g. you passed a number where a string was expected, the output woul show ERR!. Move your mouse over it to get a better description of the problem.

Examples

Assume that we have a project with the following data.

We'll now look at a few simple examples. We shall assume that the formula is attached to projects and the sample output is for the project described above.

Advanced Example: Your own schedule health indicator

Let's say that you want to have a schedule health indicator that is based on baselines i.e. the date you actually promised to the customer rather than on the current plan's finish date.

You will create a formula field, attach it to projects, set it's output data type to Text and enter the formula as:

${
pc = entity.actualPercentComplete;
pFinish = entity.projectedFinishCalendar;
bFinish = entity.baselineFinish;
now = Date.now();
label = 'Unknown';
label = Date.before(pFinish,  bFinish) ? 'On Time' : label;
label = Date.after(pFinish, bFinish) ? 'At Risk' : label;
label = Date.after(now, bFinish) ? 'Overdue' : label;
label = pc == 100 ? 'Completed' : label;
label
}

In the Color part of the formula put the mappings as:

You can search for objects based on keywords using the search box on the top right side of the main toolbar. The following table describes what is searched:

Search Options

• To search for a phrase, enclose it in " e.g. "sales tax"
• To exclude a term, prefix it with - e.g. -Microsoft
• To make a term mandatory, prefix it with + e.g. +penguin
• To search for a prefix, suffix it with a * e.g. docu* will search for all words starting with docu

Celoxis provides a feature-rich mobile optimized interface that can be accessed from any iOS, Android, Windows Mobile, Tizen, or any other mobile device with a modern web browser. There is no need to download or install any application. You will be taken to the mobile interface automatically upon accessing the application from your browser.

Celoxis gives you the ability to turn some features and capabilities off. Once you turn them off, all fields, actions and menus associated with that module are no longer shown thus simplifying the user interface. You can turn them back on anytime. For example, if you turn off the Expense module, you will see all expense related menus from the main menus, report columns & filters, and task actions disappear.

To enable or disable features, go to the Administration page and turn features on or off as indicated below:

To upload your logo, click AdministrationAccountUpload Logo. The restrictions on the image dimensions and size will be indicated on the form.

The company settings form allows you to configure behaviour and defaults for your users. It also allows for entering your Single Sign-On settings.

Some of the non-trivial settings are:

• Company Code – A business ID. We recommend that you enter the second level of your domain name here. E.g. acme.com should enter acme here.
• Document Language – Celoxis uses a search engine library that will behave differently when you are mostly going to enter CJK text
• Week Starts On – This determines the first day of the week shown in calendars
• Min Days in 1st Week – This determines whether the week of 1st January lies in the 53rd Week of the previous year or 1st week of the current year.
• Fiscal Year Starts – This determines where a date lies in Q1, Q2, Q3 or Q4.
• Allow Personal Dashboards – This is covered in the chapter on dashboards

Single Sign-On

This topic has been covered in depth in this chapter.

You can access Celoxis with corporate credentials if SAML-based SSO is enabled for your account. Celoxis works with Google, Salesforce, Okta, OneLogin and Microsoft ADFS; although any SAML 2.0 based IDP should work.

For SSO to work, ensure the following:

• Your SSO Identity Provider (IDP) is SAML 2.0 based.
• All your users, clients have unique email addresses.
• The email address of a user in Celoxis matches the email address for that user in your IDP.

To setup SSO, open AdministrationAccountCompany Information and click on Single Sign-On. You will see the form like this:

SSO Modes

In all modes, client accounts will continue to be autheticated using Celoxis credentials.

• None – SSO is off. Only Celoxis credentials can be used to log in.
• Test – SSO is on. SSO and Celoxis credentials can both be used to log in.
• Live – SSO is on. Only SSO can be used to log in.
  • Your users will not be able to Forgot Password link in Celoxis since we will not store user passwords.
  • You will not see the Login and Password fields on the add/edit user forms.
  • If you are locked-out for any reason, contact us and we shall reset your SSO details.

Steps in setting up SSO

1: Enable SSO in Test mode

Open AdministrationAccountCompany Information and go to the Single Sign-On tab

1. From the Status row, click on the Test radio button.
2. From the options below, copy the ACS URL. This will be required to setup your IDP.
3. Setup your IDP. The IDP will give you a set of settings to enter into Celoxis.
4. Come back to this screen with the settings collected in the previous step.
5. Enter the IDP Entity ID. This is provided by the IDP.
6. Enter the IDP URL. This is the address of your IDP which will be contacted for autheticating users.
7. Copy - Paste the IDP Certificate. This information is available in the certificate provided by your IDP.
8. Click Save

2: Test your setup

1. After your step 1 is complete, you should try login to Celoxis by clicking on the Connect via Single Sign-On link on the Login page.
2. After you click on the above link, you will be prompted to enter the email address.
3. After entering this, you are directed to your IDP login screen; if not already logged in, where you are prompted you to enter the Email and password.
4. After successful authetication, you are directed to Celoxis Dashboard. If something goes wrong, have a look at the Common Errors section under your IDP.

3: Go Live with your SSO

1. After you have successfully completed step 2, review your SSO details again.
2. Then, click on Live.
3. Click on Save.

Setting up your IDP

Before you set up Celoxis, you will first need to tell your IDP about Celoxis. The following are the instructions for some of the popular IDPs. If your IDP is not listed here, please consult its documentation.

All IDPs will require an ACS URL for Celoxis. You can find this for your organization by clicking on Test or Live radio buttons as shown above.

In many organizations, Jira is still the key software for developers, while project managers and PMO want to use a project management software and still have visibility into resource workloads.

With this integration, you will be able to automatically create tasks in Celoxis when issues are created in Jira. Also, when issues are updated in Jira, the corresponding tasks in Celoxis will be automatically updated.

Zapier

Celoxis integrates with Jira and many other apps using Zapier. Zapier is a cloud-based service that allows you to build powerful integrations between different systems without writing code. For more information, visit their website: zapier.com.

Zap

An automation in Zapier is called a zap. A zap connections two apps - a trigger app and an action app. The trigger app notifies the zap about an event and the zap then performs an action in the action app. In our case, the trigger app is Jira because it will notify our zap when an issue is created or updated. The action app, in our case, is Celoxis because that is where our zap will create and update tasks. In this guide, we will be building two zaps:

• Zap #1 — when an issue is created in Jira, create a task in Celoxis.
• Zap #2 — when an issue is updated in jira, update the corresponding task in Celoxis.

Let's see how Jira, Zapier and Celoxis all fit together:

From the above diagram, you can see that Jira and Celoxis can even be on our intranet provided they have access from the internet. It may be possible to configure internet access only from Zapier.