CALCULATION FRAMEWORK USER GUIDE. Basic configuration for version 4.02

Transcription

1 CALCULATION FRAMEWORK USER GUIDE Basic configuration for version 4.02

2 COPYRIGHT Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Wavextend B.V. As the software licensee, you may make reasonable customizations to the software online help documentation for your internal use only. You are solely responsible for and bear any and all liability relating to any customizations you make. This includes any adverse effect that your customizations have on any functionality of the licensed software, the software documentation itself or otherwise relating to use of your customizations. Please note that installing software upgrades may rewrite customized online help files. Wavextend may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Wavextend, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property Wavextend B.V. All rights reserved. Calculation Framework user guide, Basic configuration for version

3 VERSION This version of the user guide for Calculation Framework is valid for Dynamics CRM 4.0 in combination with Wavextend Calculation Framework 4.02 only. There are different user guides per version available on the Wavextend website: The target group for this guide consists of application consultants that are unfamiliar to Wavextend Calculation Framework or power users that will perform simple calculation configuration without assistance of their implementation partner. In either way you are encourage you to take the Microsoft course on Customizing Dynamics CRM 4.0 because it will significantly improve your understanding of the Calculation Framework options. In addition to this manual there is an Advanced Calculation Framework configuration guide which will introduce you in the endless possibilities of complex calculations or automations, dives into deploying calculation configurations on different servers and provides tips for issue tracking. Reading the two guides will give you a profound background to professionally use Wavextend Calculation Framework and provide the power to reduce much of the required.net and Javascript coding for Dynamics CRM. In case you have remarks, preferably constructive feedback, on this guide. Please send a mail to its authors at userguide@wavextend.com The latest version of this guide will be published on the Wavextend website. People who send feedback will be automatically notified of the availability of new versions until an unsubscription request is received. Calculation Framework user guide, Basic configuration for version

4 TABLE OF CONTENT Copyright... 2 Version... 3 Table of content... 4 Introduction... 5 How to configure a simple calculated attribute... 6 A single entity calculation... 8 An aggregated calculation A value copy How to execute a calculated attribute Run a calculated attribute manually Monitor execution result Configure a schedule Execute a schedule Calculation Framework user guide, Basic configuration for version

5 INTRODUCTION Thank you for trying, or better buying, Calculation Framework from Wavextend. This user guide will lead you through the basics of calculation configuring. After reading this user guide you will be able to: 1. Configure basic calculated attributes 2. Test your calculated attribute 3. Execute a calculated attribute 4. Schedule a calculated attribute With these new skills you will be able to perform most common tasks and configurations in Calculation Framework. As a result you will have gained the power to significantly expand the possibilities of Dynamics CRM. Some examples are: Customer segmentation and customer value calculations Relation-roles Customer reports Performance Management International address lines and salutation headers International phone number formatting Order and or case invoicing This guide assumes you have been able to install Calculation Framework on your Dynamics CRM server, or better have had someone else to do it for you. You can find more information on how to install Calculation Framework on the website: Make sure you have the Wavextend: User or Wavextend: Administrator role and belong to the Wavextend: Calculated Attribute Views Team team. In all examples the standard Microsoft Adventure Works Cycle database is used which is available for download on the Microsoft website. Some custom attributes were added to this sample database for example purposes. The procedure for deploying the customization file is not part of this guide. Please refer to the Microsoft Dynamics CRM documentation for further instructions. Calculation Framework user guide, Basic configuration for version

6 HOW TO CONFIGURE A SIMPLE CALCULATED ATTRIBUTE The first step in configuring a calculated attribute is to find it in the user interface. To do so you will need to go to: Settings -> Wavextend > Calculated attributes Figure 1: Screenshot of Calculated Attributes in Dynamics CRM. Of course this works in a similar way in the Outlook client. Depending on your previous activity or that of your colleagues, you will have none or more preconfigured calculated attributes in the list. The second step is to hit the New button and open up a new calculated attribute form that will look like the following: Figure 2: Screenshot of new calculated attribute form Calculation Framework user guide, Basic configuration for version

7 You are recommended to give your calculated attributes descriptive names, so it is easy for you to find them in the big list you might end up with. Maybe there is a naming convention in your organization you will need to be aware about, or should be considered. The description field will provide more room for descriptive info like the purpose or usage of the calculation. The processing order field could be relevant for scheduling but is left for the scheduling chapter. The third step is to determine the type of calculation. The type will be determined by the expected use of other attribute values in Dynamics CRM and their relation with the target attribute. The target attribute is the attribute in the Dynamics CRM domain model where you wish to store the results of the calculation. You will have three options: 1. Single Entity Calculation Use a single entity calculation in case you expect to only use attribute values belonging to the same entity as the target attribute (the current entity) or if you plan not to use other attributes values at all (like setting default values). 2. Aggregated Calculation Use aggregated calculation if you plan to use attributes of downstream entities having a direct 1:N or N:N relationship with the current entity and perform aggregation calculations on them like averages or summations. 3. Value copy Use value copy if you plan to use attributes in your calculation from upstream entities (or lookups) in relations to the current entity. The most common use is to copy values like a phone number from a customer to the opportunity or case. But of course you will have the option to do more advanced logic as well. In the following section you will see an example of all three types of calculations and their steps. Calculation Framework user guide, Basic configuration for version

8 A SINGLE ENTITY CALCULATION To create a simple calculation please select the type Single Entity Calculation and the screen will show all the relevant fields for this type of calculation looking similar to the following: Figure 3: Screenshot of a Single Entity Calculation In this example two new custom attributes were used that were added to the order entity. One named cost price and the other called margin. Both attributes were placed on the main form and margin was made read only as will be the case in most target attributes. A couple of records were created to be sure there are some test results. TIP: Put something in the description field of an attribute that will say it s a calculated attribute. Configuring any calculation will require six steps: 1. Give it a name, description and type ( Single Entity Calculation ) 2. Specify the target 3. Specify an optional source 4. Specify the calculation 5. Save your configuration Calculation Framework user guide, Basic configuration for version

9 6. Test the calculation The target section allows you to specify where the result of your calculation should be stored. You will start with selecting the correct entity. In this example choose Order. Next, you will select the attribute that belongs to the selected entity. Depending on the type of installation you will have a list of all attributes in the CRM installation or only the attributes belonging to the target entity. Be careful not to select an attribute belonging to the wrong entity. If you do select an attribute belonging to the wrong entity, you will not be able to save the calculated attribute. Figure 4: Selection menu for attribute. Only select attributes with a Present status reason because others will fail the calculation. The following step is optional and allows you to set a limit to the scope for the target records. For example: only orders with an amount (not null) or only order of this year. To do so you will have to prepare a saved view using the standard advanced find in Dynamics CRM. You can find loads of information on how to use the advanced find in materials from Microsoft or on the web so this topic is not further discussed in this guide. Calculation Framework user guide, Basic configuration for version

10 Figure 5: example of a saved advanced find query You can create or select this view under the Target Filter lookup button. You will only be able to see your own saved views or those shared with you. Figure 6: Selection of a target filter TIP: In an appropriate setup of calculation framework all configurators are added to the Wavextend: Calculated Attribute Views Team team. This will allow you to automatically share all views used for calculation configuration and membership is necessary for importing and exporting calculation configurations (not further discussed in this guide). The custom target filter is not further discussed in this guide but saved for the advanced course. Calculation Framework user guide, Basic configuration for version

11 The third task is to define a source for those calculations that will use other attribute values in the calculation. This applies to almost every calculation where you do not have the intention to set the target attribute with a static default value. How to set a static default value is demonstrated in the last part of this chapter. The source section contains those attribute you would like to use as variables in your calculation expression. A single entity calculation is configured, so you should choose attributes coming from the current entity (same as target attribute entity). In this example order. The expression used to calculate margin in this example is: Margin = Total Amount Cost price So in the source section two source attributes are chosen, being Total Amount and Cost price, both belonging to the Order entity. The result will look similar to this: Figure 7: Source section The final step in calculation configuration is to set the calculation operator in the calculation section. In this example it is set to: Substract And hit Save to store your calculation configuration to be able to test it and run it. The result of this calculation configuration is as follows: [Target Entity].[Target attribute] = [Target Entity].[Source Attribute 1] [Target Entity].[Source Attribute 2] And it will only do this for the target records that are returned from the [Target Filter] view. Calculation Framework user guide, Basic configuration for version

12 To see the result of the calculation (without updating data in the Dynamics CRM database) you hit the Test button (only appears after save). As result you can now see a pro forma calculation for your configuration. Figure 8: Test result The test result will only display records that were selected as result of the Target Filter and shows the changes that would be made to the database in case you would execute the calculated attribute. The first column shows the primary attribute of the Target Entity, the second column contains the value of the Target Attribute before update and the third columns contains the value of the Target Attribute after update. Calculation Framework user guide, Basic configuration for version

13 You will have two additional options to check the result. One is to use the Changes Only button to filter only the records that would actually be updated by the calculation. The other option is to open the form of a record, by clicking on the first column of the record row. In that way you can check for yourself if the source variables would give you the expected result. The View Query button is an advanced topic and not further discussed in this guide. Congratulations, you have now configured your first calculated attribute. Before you execute it (look in the execution chapter) here are some important things to remember: NOTES: 1. In case the result of the calculation fall out of boundary, (min, max or size property of the target attribute) the New Value will turn red. 2. If you choose incompatible source attributes data types (like subtracting string values to return a money attribute) you will receive an error messaging saying the specified operator is not valid for the selected attribute types. or a SQL error that will provide more information on the invalid cast. 3. Some calculations require more than two source attributes with a calculation operator. For example the Margin in % = Total Amount Cost Price / Total Amount. In that case you need to split the calculation up in steps like the following: a. Margin in money = Total Amount Cost Price b. Margin in percentage = Margin in money / Total Amount You will learn how to execute the two different calculated attributes in the right order in the scheduling chapter. The other option is to use advanced calculations but these are not further discussed in this guide. 4. In a simple single entity calculation you will typically not set a source filter or custom source filter. In addition to configure a calculation you can also use Single Entity Calculation to set a static default value. There are two scenarios where you should consider this. The first is when you create a custom new attribute with a default value in a database that already contains data. Dynamics CRM will fill the default value for all new records but existing records will have empty values. In that case a calculated attribute with a corresponding static default value, executed once, will help you. The second scenario is when you want to set conditional values. Such a case is shown in the next example. In this example the purpose is to set the relation type attribute of an account to customer in case an account has an order submitted in the past with a positive amount. The first step in doing so is to prepare an advanced find view that filters all accounts that have an order submitted in the past with a positive amount. Calculation Framework user guide, Basic configuration for version

14 Figure 9: Advanced find view preparation query You save this view with a descriptive name like Accounts with order. This view is selected in the configuration as the Target Filter Now configure a calculated attribute like in the following screenshot: Calculation Framework user guide, Basic configuration for version

15 Figure 10: Example configuration of a conditional default value. As you will see in the screenshot, no source attributes were used and as a Calculation Operator Custom is selected. The Custom Calculation field will contain the default value. In this case which corresponds with the value of the picklist of relationship type customer. Calculation Framework user guide, Basic configuration for version

16 The test result window now looks as follows: Figure 11: Test result window of conditional default value NOTES: 1. To set an unconditional default value, just leave out the Target Filter 2. Hierarchical conditions can be accomplished using two different calculated attributes in the right order which is show in the Scheduling chapter. For example: An account with opportunities is a prospect unless the account also has an order which makes it into a customer. 3. Notice you are not limited to calculate set numeric or money fields, but also picklists. In addition to that you can even set dates, string values and so on. Every data type is supported except for Lookups. (but still possible with a special tweak which is discussed in the installation guide). 4. To set the default value of strings enclose the string with single quotes like default value AN AGGREGATED CALCULATION The second type of calculation configuration to show is an aggregated calculation. An aggregated calculation comes in handy for all those scenarios where you: Calculation Framework user guide, Basic configuration for version

17 1. Want to see a total on a form, like number of complaints for this customer on the account form. 2. Want filter on a total in an advanced find, like select all customers that spend more than x this year or select all customers that had no orders this year. 3. Want to export a total for bookkeeping for instance, like export the total amount to be invoiced for this case based on the hours spend on the service activities x the rate of the resource. 4. Set a conditional branch in workflow based on a total like if the total amount for this customer this year is more than x and the customer puts in a complaint, please call the customer right away otherwise send an excuse letter. All these and many more scenarios are made possible in Dynamics CRM exclusively using Wavextend Calculation Framework. To configure an aggregated calculation you need to perform the six following steps: 1. Give it a name, description and type ( Aggregated Calculation ) 2. Specify the target 3. Specify a source 4. Specify the aggregation calculation 5. Save your configuration 6. Test the calculation One and two are skipped because, except for to the type, they are exactly the same as the previous chapter. The difference starts with the source. In the source section, you need configure the following in corresponding order: 1. The Source Entity. This is the entity where the data used in the aggregation calculation will come from. For example order. 2. The Relationship. You will need to specify which relationship (1:N or N:N) will apply to the Source Entity and Target Entity. Most of the time there is only one valid relationship like the order_customer_accounts relationship for example. In some cases there will be more than one relationship available and you will need to choose the right one. Look in the customizations configuration and the descriptions for more info on which relationship to choose. 3. The Source Attribute 1 to specify which attribute should be used in the aggregation and belongs to the Source Entity 4. Optionally a Source Filter like only orders submitted this year to ensure only year to date orders are aggregated. Calculation Framework user guide, Basic configuration for version

18 Figure 12: Source configuration for aggregated calculation Custom Filter is skipped for explanation until the advanced guide. In the calculation section you can specify which type of aggregation has to be performed on the Source Attribute 1. To do so, select the appropriate aggregation option in the Aggregation Operator list of options. Figure 13: Aggregation Operator selection Here is an explanation of the different options: 1. Sum, will add up all found values of the Source Attribute 1 belonging to the same Target Entity records in relation to Relationship optionally filtered by Source Filter 2. Average, will add up all found values of the Source Attribute 1 belonging to the same Target Entity records in relation to Relationship optionally filtered by Source Filter and divide it by the number of found values. 3. Maximum, will pick the largest value out of all found values of the Source Attribute 1 belonging to the same Target Entity records in relation to Relationship optionally filtered by Source Filter 4. Minimum, will pick the smallest value out of all found values of the Source Attribute 1 belonging to the same Target Entity records in relation to Relationship optionally filtered by Source Filter Calculation Framework user guide, Basic configuration for version

19 5. Count, will count the number of records found belonging to the same Target Entity records in relation to Relationship optionally filtered by Source Filter 6. Count distinct, will count the number of unique values found of the Source Attribute 1 belonging to the same Target Entity records in relation to Relationship optionally filtered by Source Filter 7. StdDev, will first add up all found values of the Source Attribute 1 belonging to the same Target Entity records in relation to Relationship optionally filtered by Source Filter and divide it by the number of found values and second adds up the difference of all found values of the Source Attribute 1 with the result of the first step and divide it by the number of found values. In other words a standard deviation or average difference calculation. 8. Custom, will allow you to use default values or advanced SQL expressions that are discussed further in the advanced guide. NOTE: Not every aggregation calculation is applicable to all data types. The following table shows which aggregation is dependent on the used data type: Sum only numeric data types and money data types Average only numeric data types and money data types Minimum all data types Maximum all data types Count all data types Count distinct all data types StDev only numeric data types and money data types Custom all data types Calculation Framework user guide, Basic configuration for version

20 Now let s have a look at a typical example of an aggregated calculation configuration: Figure 14: Example of aggregated calculation configuration. In this example the following is calculated: [Account].[Annual Revenue] = SUM([Order].[Total Amount]) where [Order].[Date Submitted] equals This year and *Account+ is related to *Order+ through the*order_customer_account+ relationship. NOTES: 1. You are permitted to combine Target Filter and Source Filter. The first will determine the scope of the records to be updated and the second will determine the scope of the values used in the calculation. 2. More complex aggregation calculations are possible of course but leave you two options. Either you choose to read and learn from the Advanced Guide, or you break up your calculation into multiple separate simple calculations and execute them in the right order as discussed in chapter Scheduling. Calculation Framework user guide, Basic configuration for version

21 A VALUE COPY A Value copy (N:1) type of calculation is used when attributed coming from an upstream entity or Lookup as they are called in Dynamics CRM are used in the calculation expression. Most of the time you will find yourself copying values from an upstream entity, like a mapping in the relationship configuration of Dynamics CRM. Some examples of scenarios: 1. Copy the customer s phone number on every running opportunity every time the customer contact data is updated. 2. Copy the type of support contract from a customer to the case every time a new case is created or on running cases when the type of contract on the customer is updated. These examples and many more mappings are made possible in Dynamics CRM exclusively using Wavextend Calculation Framework. The explanation on how to calculate with value copy calculations is saved for the Advanced Guide. The calculation option is now optional and always custom. If you leave it blank it will just copy the selected 'Source Attribute 1 into the Target attribute Here s an example of a valid Value copy (N:1) calculation: Figure 15: Example of value copy calculation This example will copy the value of the [Account].[Address Phone] into the [Opportunity].[Description] field where [Account] is the customer lookup for [Opportunity] NOTES: 1. The data types of Target attribute and Source Attribute 1 will need to be compatible. Calculation Framework user guide, Basic configuration for version

22 2. These value copies look similar to relationship mappings in Dynamics CRM but are very different. A mapping in Dynamics CRM is only called on creation of a related entity. (like create opportunity from account). This makes it a static mapping and is limited to creation from the account form. It will not be updated after initial creation of the related entity and is not updated upon change of the lookup. These things can be accomplished with a value copy calculation which makes it a dynamic mapping. 3. Value copy of Lookups are unsupported by Microsoft but can be accomplished with a special system tweak which is described in the tweaking guide. Calculation Framework user guide, Basic configuration for version

23 HOW TO EXECUTE A CALCULATED ATTRIBUTE In the previous chapters you learned how configure calculated attributes using Wavextend Calculation Framework. It s now time to put you calculations to action. To execute a calculated attribute configuration you have many different options depending on your specific requirements or situation: 1. Execute it manually. This is for ad hoc purposes. Like setting an initial value or a default value or for manual maintenance jobs 2. Execute it as part of a schedule. This will update a number of calculated attributes in a batch. You will have two options: a. Run the batch manually. b. Run the batch periodically in a predefined schedule 3. Execute the calculated attribute as part of a custom workflow. Use this option if near real time information is important for your business. You can trigger the calculation in two ways: a. Run the calculated attribute for all applicable records. b. Run the calculated attribute only for a record related to the workflow record. 4. Execute the calculated attribute as a result of an onload, onchange or onsave event on the entity Form. 5. Execute the calculated attribute as a result of a webservice call from a custom plugin. Manual execution is discussed in this chapter. Scheduled batch execution is clarified in the next chapter. OnForm execution, SDK and Execution as part of workflow is not further explained in this guide but as part of the Advanced Guide. RUN A CALCULATED ATTRIBUTE MANUALLY To manually run a calculated attribute you need to use a workflow. Navigate to your list of calculated attributes and select the attributes you would like to execute. Hit the workflow button and select the Wavextend: Process Calculated Attribute workflow. Calculation Framework user guide, Basic configuration for version

24 Figure 16: Manual execution through workflow NOTES: 1. Running the workflow is also accessible from the calculated attribute form 2. Running multiple selected calculated attributes in this way will not comply with the order field, which is discussed in next chapter. MONITOR EXECUTION RESULT You have the ability to view the progress and success or failure of your execution. To do so, open up the form of your calculated attribute and navigate to the workflow side menu. Figure 17: Workflow status on execution of a calculated attribute The workflow will start with an initial status of Waiting for response and when started will switch to status In progress to round up with status Succeeded. Be careful, this last status does not imply that the execution has a successful result. It just tells you the workflow has finished doing what it needs to do. To check if the calculation was executed properly, navigate to the log side menu, after successful workflow execution to see the following: Calculation Framework user guide, Basic configuration for version

25 Figure 18: Logging In this example the Margin on an order calculated attribute was executed four times of which the first three times were successful and the last execution completed with rejections. To find more information on the problem, open up the log record with the Completed with rejections or even worse Failure result. Figure 19: Log details The message displays additional information about the nature of the problem. In this case the Margin attribute on the order has a maximum value limit and half of the results from the calculation do not fit into the target attribute because they are out of boundary. If a more serious issue would occur, like the target attribute was deleted from the system. A failure log would arise like: Calculation Framework user guide, Basic configuration for version

26 Figure 20: Failure log details If you return to the calculated attribute form and hit the system tab, you will see that Calculation Framework has made this calculated attribute an invalid calculated attribute. Figure 21: Invalid calculated attribute If required your administrator is able to define custom workflows for handling such a situation. The valid flag is also displayed in the list of calculated attributes and also a view with the name Invalid Attributes is supplied. Figure 22: List of invalid Attributes Correcting these kinds of problems or advanced issue tracking is not part of this course. Calculation Framework user guide, Basic configuration for version

27 CONFIGURE A SCHEDULE The Wavextend addons for Dynamics CRM ships with a build in scheduler you can use to periodically schedule the services provided by Wavextend addons or allows you to run a couple of dependent or independent calculated attributes Calculation Framework is connected to the Wavextend scheduler and this allows you to configure predefined schedules to run your calculated attributes in a batch. This is where finally the Processing order field on your calculated attribute starts playing a role. You can give the order field any numeric value you like. The processing order field will determine in which order calculated attributes belonging to a schedule batch will be executed. The execution process will start at the lowest possible order value and work its way up to the highest one. This is important if one calculated attribute is dependent on the value of another calculated attribute. Attributes without a processing order number will be processes first. A calculated attribute can be a member of more than one schedule, so make sure you leave enough room between your order numbers to fit others in afterwards. The math for doing sophisticated execution order planning is left entirely up to you. To configure a schedule you go to: Settings -> Wavextend > Schedules To create a new schedule, hit the new button, configure the desired schedule and hit save. Figure 23: Schedule example every night In the side tab Calculated Attributes you have the ability to add calculated attributes to your schedule. The other way around, from the calculated attribute form, also works. NOTES: 1. The scheduling options will be different per predefined pattern. Calculation Framework user guide, Basic configuration for version

28 2. The time is UTC also called Greenwich Time. Check on the difference between your local time and UTC time and subtract or add this to the UTC time. 3. The time can be entered both in military format as in PM / AM format. 4. The Interval field will tell you in combination with the pattern what the time is between execution. For example an interval of 1 means every day and an interval of 2 means every other day. As a check the next scheduled run field is provided (after saving the schedule). If you do not to intent to periodically execute the schedule but use it as a batch to run manually, you can set the enabled flag to unchecked. This will discard all the pattern settings. EXECUTE A SCHEDULE You have two options to execute a schedule batch: 1. Execute it manually. You do this to set initial or default values on a group of calculated attributes at the same time ensuring the execution is in the desired order. 2. Execute it periodically. Do this for a scheduled batch run. Like automatically executing a couple of calculated attributes every night. Manual execution of a schedule batch is performed by running the Wavextend: Process Schedule workflow on the selected schedule. Calculation Framework user guide, Basic configuration for version

29 Figure 24: Manually run a schedule Automatic running requires to have a valid schedule pattern with calculated attributes and the Enabled flag set to checked. The rest will go automatically. Execution as part of workflow is described in the Advanced Guide NOTES: 1. Automatic execution requires the Wavextend Background Service windows service to run on the server. 2. Having the same Processing order number is not a problem for calculated attributes as long as there is no dependency between them. Calculation Framework user guide, Basic configuration for version

30 A schedule provides logging in the logging side menu of the schedule: Figure 25: Schedule log In this example you will see that one calculation was performed successfully and one was performed with failure. Therefor the result of the schedule is Completed with errors. These log entries are connected to the calculated attribute as well of course for further investigation (see MONITOR EXECUTION RESULT). Calculation Framework user guide, Basic configuration for version

31 A Relationship, 18, 19 Advanced Calculation Framework configuration, 3 Aggregated Calculation, 17 Aggregation Operator, 18 C Calculation Operator, 11, 15 Changes Only, 13 Completed with errors, 29 Custom, 15 Custom Calculation, 15 Custom Filter, 18 I In progress, 24 Interval, 27 O Outlook client, 6 S Single Entity Calculation, 8 Source Attribute 1, 18, 19, 21 Source Attribute 1, 18 Source Entity, 17, 18 Source Filter, 18, 19 Substract, 11 Succeeded, 24 T Target attribute, 21 Target Entity, 12, 18, 19 Target Entity, 18 Target Filter, 10, 12, 14, 16 Test, 12 V Value copy, 21 View Query, 13 P Pattern, 27 Processing order, 26, 28 R Relation type, 13 W Waiting for response, 24 Wavextend Background Service, 28 Wavextend:: Administrator, 5 Wavextend:: Calculated Attribute Views Team, 5, 10 Wavextend:: Process Calculated Attribute, 23 Wavextend:: Process Schedule, 28 Wavextend:: User, 5 Calculation Framework user guide, Basic configuration for version

32 2011 Wavextend B.V. All rights reserved. Calculation Framework user guide, Basic configuration for version