The “Allow Duplicate XXX Lines” parameters described in the table above rule the insertion of duplicates in the quote, either locally or globally. Their behavior is given in the tables below.

This applies only to CT7 and CP7 types of lines.

STATUS DEFINITION

The approval process of Quote relies on a graph of statuses the user may have to go through during the quote lifecycle.

For instance when integrated with the standard salesforce.com, the status graph is as follows:

• Each status can have a list of parents allowing the implementation of complex approval processes as shown in the example above.
• Each status can be classified into one of the 3 following types: Quote / To-order / Order. Theses 3 types of the status have influence on the quote process steps displayed to the user.
  • For instance: step “Order Now” must be only visible once the quote has been accepted by the customer
• For each status a business rule can be implemented to define the possible subsequent statuses depending on the value of some business indicators
  • Such as total revenue, % of margin, % of discount, etc. which have been computed in the quote
• After having changed a quote status, some actions may automatically occur.
  • For instance: The generation of an email assigning a quote review task to the manager of the quote ownerThe status graph is made-up form an empty list. Each status is associated with a set of properties detailed in the table below:

Refer to Using External Java Class Refer to Macros

Upon review of a quote the end user is able to post a comment for his/her review. In the default quote model, the latest comment is saved in the ChangeStatusComment field of the Parameter tab. It is then possible to synchronize this field to the CRM (Salesforce, Dynamics,…) by implicit mapping.

If you are dealing with large quotes, activating the mass mode allows to optimize the spreadsheet actions when manipulating high numbers of lines.

When the Mass Mode is set to ‘On’, the triggers associated with the actions on lines and sublines are called in a way more adapted to large volumes of data.

In details, the triggers concerned by the Mass Mode are the following:

To improve the performances of your triggers by using the mass mode, you could define macros that will test if the corresponding action is unitary or has to be performed on a set of lines. To do so, you just have to test if the rowsSelected table contains elements (mass mode) or not (unitary mode), and execute your action accordingly. Here is an example of macro that can be used in that way:

DEFINE my_Update_Before()

COLUMN DEFINITION

Spreadsheet columns are fully customizable. They are built-up from an empty grid into which any type of fields can be added.

Reference: Refer to Focusing on Field/Column/Total Cell to learn more about the properties attached to the fields.

The limit is governed by the database storage capacity as well as by the cloud edition (SaaS deployment only) as detailed in the tables below:

Propagation Definition

Three types of computations can be defined for each column:

• Horizontal calculation (green arrows in the example below)
  • Horizontal calculations allows cells to be calculates from other cells of the current line
    • Horizontal calculations are specified for each type of line/subline in the input mode of the column.
• Vertical up propagation (blue arrows in the example below)
  • Up propagation allows parent cells to be calculated from its child lines.
    • Up propagation are specified for each type of line/subline in the Up Propagation rule of the column
• Vertical down propagation (red arrows in the example below)
  • Down propagation allows cells to be calculated from the parent line.
  • Down propagation are specified each type of line/subline in the Down Propagation rule of the column

The following tables illustrate the calculations carried out for an example model.

OnDemand Grid Actions

On Demand actions can be displayed in the menu bars at the top of the spreadsheet. These actions may be predefined (access to the quote header, change status, XML export, save, etc.) or specific.

In all cases, these actions are declared according to the properties detailed in the table below:

OnDemand Line Actions

At runtime, from the spreadsheet an “onMouseOver” flyer comes up, allowing the user to access various actions applicable on line(s) selected beforehand according to their scope of application defined by;

• The number of lines selected:
  • Single (only one line may be selected)
  • Multiple continuous (several consecutive lines may be selected)
  • Multiple discontinuous (several lines which do not have to be consecutive may be selected)
• The authorized type of lines (FO, SP, CP7, SI7, etc.)

These actions can be predefined (copy, paste, delete, item record, etc.) or specific.

In all cases, actions are declared according to the properties detailed in the table below:

Automated Actions

At runtime, automated actions can be raised on events linked to the quote spreadsheet. For example: trigger a message when the margin threshold exceeds…

Reference: Refer to APPENDIX C – Focusing on Events

Automated actions can be predefined or specific. In all cases, they are declared according to the properties detailed in the table below:

• By default, if no type is declared in the quote model, the Breakdown type of link is taken into account to create LNKCT lines)
• Multiple product link types may be mapped

CONFIGURATOR

Adding a Configured Product

The product resulting from the configuration process creates a line (CP7) in the quote spreadsheet. If a configured product is modified, its line is updated. Each column evaluated with XPath queries are executed from the XML file resulting from the configuration process.

The configured product may be broken down into sub-lines. In this case, sub-lines belonging to the

parent line will be created in the spreadsheet. Similarly, each column evaluated with XPath queries are executed from an extract of the XML resulting from the configuration process.

Actions associated with the Configurator

Updating a Configuration Variable

Within the spreadsheet, the user can directly update configurable variable without returning to the

configuration process. The update is automatically sent to the Configurator as a background task. Line and sublines are then refreshed with the modifications arising from the configuration result.

In the example below, the color, height and width of the product configured may be changed in the spreadsheet:

• The input mode must be "Direct Configuration Update"
• The horizontal calculation must be setup with a XPath query targeting the value to be retrieved
  • Example

    : /conf:ConfigurationTree/conf:ConfigurableProduct/conf:Form[@cpe='CPE.workspace/C P/myCP.workspace/FO/myFO']/conf:FormProperty/conf:SingleValuation/conf:Value/onf: integerValue

• Following additional properties must be setup to automate the update from the spreadsheet:
  • cpeOfFP = CPE of the targeted question (FP)
  • Example:
  • CPE.AC/CP/RootCP.AC/CP/CP13.AC/FO/Form1CP13.FP/fpBooleanForm1CP13)
  • typeOfFP = "VALUE", "QTY", "COMMENT" depending on which property of the question to be updated
  • typeOfValuation (optional) = "BOOLEAN", "DATE", "FILE", "INTEGER", "LONGTEXT", "MONETARY", "NUMERIC", "PK", "TEXT", "URL"

Important Note on Format: the variable format in the quote and configuration should be identical for the update to be successful. In the case of Date and Boolean variables, because the format is different between the configuration and the quote, one should use intermediary columns / FPs to ensure that the right conversions are performed for the Conf Update to be successful.

• Only variables belonging the "root" context can be updated (update in looped instances is not supported)
• If the structure of the configured product is modified after the value of the variable has been changed, certain data belonging to line or sub-lines may be lost (for example, manual discount entered on a sub-line which no longer exists).
• Values format should be the same on configurator and cart side. In some cases (Dates for example) it is impossible to have a same format on both sides.

  In such cases one would need to create additionnal columns, FPs and logic on the model (configuration and quote) to perform the necessary conversions.

Mapping between the Configurator and the quote lines

The table below details the mapping mechanism between the breakdown lines issued from the configuration process and quote line/subline types.

To generate LNK type of sublines mapped with custom product links (different to the standard one of type breakdown) the steps described below must be followed:

1. Declare in the configuration file of the Configurator a custom saving policy which includes the custom product link(s) to be stored in the XML file:

   For instance:

   <cam:Param cpe="CPE.Settings.Session.SavingPolicy" value="Custom; configurationDetails=true;

   domainDetails=false; generativeProcess=true; notExisting=false;

   productDictionary=true; productLinkType= "customLink1~customLink2" />

2. Declare in the general settings of the spreadsheet the custom link type to be mapped with the subline of type LNK (refer to chapter General Settings)
3. Use XPATH mechanism to retrieve information from the product links (like the other type of lines)

• By default, if no type is declared in the quote model, the Breakdown type of link is taken into account to create LNK lines)
• Multiple product link types may be mapped

Synchronization column concept

The Sync column allows the end-user to re-launch configuration process associated with configured product while keeping manual entries made in the spreadsheet (e.g. discounts, tax etc.). This mechanism applies if and only if the SyncID remains identical after each re-launch.

• Identify the column to store the SyncID : set the property “Sync Column” to ”Yes”
• The SyncID could be for example retrieved via XPATH of the CPE of the Codified Line, or the CPE

  of the Matched Item.

• Before accessing the configuration process an image of the configured product breakdown is memorized with included the values of the editable columns
• After the configured product lines and sublines have been re-created, the editable values are re-applied and the propagation are launched, simulating thus, the user inputs (from the top line (root) to the bottom line and from the left to the right.)

NEGOTIATION TOOLS

The quote spreadsheet embeds tools to help the users to determine the right price and quickly adjust quoted prices that do not align with financial objectives:

Pricing and Discount Guidance

The guidance thresholds (up to 5 levels) displayed in the widget associated to the Guidance type of column can either come from CPQ (predefined) or PROS PO (predictive).

In addition, a maximum and minimum value must be provided as well.

The visual scale between thresholds, min, max, and current value is respected in the diagram.

At the top, a header presents the different thresholds defined, and their associated value. You can click on one of the threshold to assign its value to the guidance widget.

Discount and Pricing guidance can be handled:

• Example of a Pricing Guidance:
  • The column is used to store the final discounted price.
    
    
• Example of a Discount Guidance:
  • The column is used to store the discount (in percentage or in amount) to be applied on the List Price (Max. Price)
    
    

The guidance column parameterization has to comply to the following rules:

• The type of the guidance column AND the type of the columns containing the levels have to be identical (e.g. For a Discount Guidance stored as a Percentage, the target/expert/floor level columns have to be Percentages)
• A minimum of 2 levels ((Expert and Floor) are necessary to render the widget
• The Maximum price is mandatory. The Max. Price column is considered as the List Price i.e. the price corresponding to a 0% discount.
• The values of the levels have to be correctly ordered:
  • For Pricing guidance: Expert > level-2 > ...> Floor
  • For discount guidance: Expert < level-2 < ...< Floor

Finally, it is recommended that the column is Computed in addition to ‘UserInput’ to predefine the default guidance value.

Edge cases:

• If the user tries to input a value that is below the minimum value, then the minimum value is applied
• If the user tries to input a value that is above the maximum value, then the maximum value is

  applied

• When trying to open the guidance widget, if the current discount is beyond the min / max values, the guidance widget will still be displayed. The graph won't be able to present the current value. You can use the guidance header to select one of the thresholds and set the guidance value.

  This helps user getting "back on track" if they have manually assigned an invalid value from the

  
  
  
• The guidance widget can handle negative values.

The following CSS classes are is associated to the component:

.level-1 {

background-color:$Score1-Color;

fill:$Score1-Color;

}

.level-1.off {

background-color:$Score1-off-Color;

fill:$Score1-off-Color;

}

Level-2 to 5 are also available. The last level is identified by a different class : .level-red

.level-red {

background-color:$Score-red-Color;

fill:$Score-red-Color;

}

.level-red.off {

background-color:$Score-red-off-Color;

fill:$Score-red-off-Color;

}

Scoring

The scoring type of column (or type of total cell) stores an integer (from 0 to 100 – the score can be computed) and is used to render a visual indication of the quality of the negotiation on the quote line and/or on the full quote.

It is possible to define up to 5 thresholds for the scoring. For example:

• If the currentScore >= Level-1 Score (Expert), the ‘level-1’ class is used and corresponds to the green color in the default theme.
• If Level-2<= currentScore < Level-1, the ‘level-2’ class is used.
• If Level-3<= currentScore < Level-2, the ‘level-3’ class is used.
• If Level-4<= currentScore < Level-3, the ‘level-4’ class is used.
• If Level-5<= currentScore < Level-4, the ‘level-5’ class is used.
• If currentScore < Level-5, the ‘level-red’ class is used and corresponds to the red color in the default theme.

Example of rendered UI:

The following CSS class names are used to render the scoring column :

.level-1 {

background-color:$Score1-Color;

fill:$Score1-Color;

}

.level-1.off {

background-color:$Score1-off-Color;

fill:$Score1-off-Color;

}

Level-2 to 5 are also available. The last level is identified by a different class : .level-red

.level-red {

background-color:$Score-red-Color;

fill:$Score-red-Color;

}

.level-red.off {

background-color:$Score-red-off-Color;

fill:$Score-red-off-Color;

}

The “keycolumns” entity requires to specify the columns that one wishes to use for the comparison,

separated by a tilda ~.

For instance, if you look for changes between two contracts on columns DateBeginning, DateEnd and Totalprice, you will have to configure it as follows:

<automatedAction>

<name>CLMQuoteCompareAndMerge</name>

<trigger type="StatelessExecutionMode"/>

<actionType>JavaClass</actionType>

<settings>

<nameValueEntity name="javaClass" value="com.sfdc.integ.output.

CLMQuoteCompareMergeStatelessAction"/>

<nameValueEntity name="keyColumns" value="DateBeginning~DateEnd~TotalPrice"/>

</settings>

</automatedAction>

CLMCreateQuoteFromContract

<automatedAction>

<name>CLMCreateQuoteFromContract</name>

<trigger type="StatelessExecutionMode"/>

<actionType>JavaClass</actionType>

<settings>

<nameValueEntity name="javaClass" value="com.sfdc.integ.output.

CLMQuoteFromContractStatelessAction"/>

</settings>

</automatedAction>

When creating the contract of an amendment, the amendment lines are compared with the original quote lines. To do that, the Managed Package has to re-inject any line that had been deleted from the original quote. The lines are injected in a specific folder with type ‘deleted’ for both folder and sublines. The idea is that at this stage (contract creation), in most cases, the quote itself isn’t going to be opened again, only the contract will be used.

But, when calculating totals, or for approvals, it is important to ignore these specific lines. You can do that by inspecting the lines type (column ContractLineType): if the value is ‘4’, it means the line was deleted and should be ignored. The same applies for triggers upon adding lines : pay attention that these ‘deleted’ lines can be injected when creating the amendment contract.

BEST PRACTICES TO COMPUTE THE CONTRACTSYNCID COLUMN

One of the challenges of the CLM functionality is to make sure that each line items that need to be compared has a unique identifier. This identifier can, but it’s not compulsory, be used for the synchronisation in SFDC. We recommend that the ContractSyncID column should be defined this way:

XML Sample

<columnDef accessRights="open" syncColumn="yes" >

…

<name>ContractSyncID</name>

…

<columnDataValidation emptyValue="NotAllowed">

<columnComputation lineType="CP7" isChildLine="no" entryMode="Computed">

<ifComputed>

<actionType>Macro</actionType>

<settings>

<nameValueEntity name="macroString" value="ComputeSyncID"/>

<nameValueEntity name="CPE"

value="//conf:ItemSalesBreakdownLine/@cpe"/>

<nameValueEntity name="ItemID"

value="//conf:ItemSalesBreakdownLine/@cpeOfItem"/>

<nameValueEntity name="ItemPK"

value="//cat:StandardItem/@cpe"/>

</settings>

</ifComputed>

</columnComputation>

…

</columnDataValidation>

</columnDef>

And the associated Macro ought to be defined as follow

Macro language Sample

DEFINE ComputeSyncID()

LOCAL timeStamp DateCreate[aliasLine]

LOCAL timeID ACDate(timeStamp, "yyyyMMdd HHmmss")

LOCAL timeString timeID.getDate("yyyyMMddHHmmss")

IF ((parents[aliasLine]<>0) AND (rowTypes[aliasLine]="CP7"))

DISPLAY CPE + "/" + ItemPK + "/" + ItemID + "/"

ELSE

DISPLAY CPE + "/" + ItemPK + "/" + ItemID + "/" + timeString

END_IF

END_DEFINE

This macro will compute the ContractSyncID for every line type defined in the column ContractSyncID and will assign to it the following:

If the line is a CP7 subline then the ContractSyncID will be

@CPE/SI@CPE/@CPEofItem

For every other line the ContractSyncID will be

@CPE/SI@CPE/@CPEofItem/TimeofInsertionInCart

USING THE COMPARISON METHOD OUTSIDE SFDC

It is possible to call the comparison method called compareAndMergeQuotes outside of the SFDC

mechanism described above (the one triggered on ‘Create Contract’). This could be useful in order to compare two quotes. It could be called from CPQ Macro Language as follows:

Macro language Sample

LOCAL hashColList ArrayList()

/* just comparing the quantity column */

hashColList.add("Quantity")

LOCAL quo1PK CartPK(/*<PK quote to be compared of the following form domain_id.release

eg : -_cart1.1>*/)

LOCAL syncColumn "ContractSyncId"

CartTools.compareAndMergeQuotes(quo1PK, Controller, syncColumn, hashColList)

• The output format can be either fixed or opened to the user choice among a pre-defined list of formats
• The setup is made through the property outputFormat of the report service which can either contains one (or a list of) output format or the value <UserChoice>
  • Examples :
    • service.MyProposal.outputFormat=PDF
    • service.MyProposal.outputFormat=PDF,RTF
    • service.MyProposal.outputFormat=UserChoice
• Report services are declared in the file service.properties and can be overloaded from the XML WS file

• From the report template:
  
  
• Declare a parameter with the required type according to the following mapping table:
  • ON/OFF parameter: java.lang.Boolean,
  • Numeric/Integer parameter: java.lang.Integer,
  • Numeric/Decimal parameter: java.lang.Double,
  • Text parameter: java.lang.String
  • Formatted text parameter: java.lang.String
  • External file parameter: java.lang.String
  • Tick the case “Use it as a prompt”
  • Associate a default value and a description
• Associate following additional properties:
  • Group: (optional) allows to gather several parameters in common groups – names are free but cannot be translated
  • GroupPosition: (optional) integer. Allows to control the order of the groups to be prompted to the user
  • listOfValues: with the following syntax "id:value;id:value;id:value" in order to setup a pre-defined list of values
  • layout=upload for parameter of type “external file upload”
  • layout=html for parameter of type “formatted text”
  • layout=LongText for parameter of type “formatted text without a WYSIWYG editor
• From the proposal step page of Quote:
  • Prompted parameters are retrieved from the main report template and displayed per groups along with their description and their appropriate input mode:
  • checkbox for Booleans
  • combo box for those having a list of values
  • upload fields for those having the property “layout=upload”
  • wysiwyg text editor for those having the property “layout=html”
  • textfield for the others
    Warning: Parameter names must not contain special characters

• This ability is provided with two optional properties associated to each parameter defined in the report template:
  • Group=
  • GroupPosition=
• The property “Group” defines the title of the section into which the parameter belongs whereas the “GroupPosition” defines the order the sections displayed in the settings page.

• Use the method .format provided in the

  package <com.cameleon.framework.business.formatters.MonetaryFormatter> as shown in the example below:

  • (new com.cameleon.framework.business.formatters.MonetaryFormatter(new Locale($F{User_Country}, $F{User_Language}), $P{User_Currency})).format(new double($F{Price1}),$F{User_MonetaryFormat})

• Retrieve in a field of type String the content of the tab “SVG” associated with the parent quote line:
  • Example:

    <field name="Drawing" class="java.lang.String">

    <fieldDescription><![CDATA[itemXML/ConfigurationTree/ConfigurableProduct/

    GenerativeProcess/ItemSalesBreakdownLine/Drawing/DrawingResult/SVG]]>

    </fieldDescription>

    </field>

• Create an object of type image "net.sf.jasperreports.engine.JRRenderable"
• Use the method “getDrawingJasper(String)” to display the graphic in the report
  • Example:

    <image evaluationTime="Now" hyperlinkType="None"

    hyperlinkTarget="Self" >

    <reportElement x="170" y="70" width="250" height="300" key="image-1" positionType="Float"/>

    <box></box>

    <graphicElement stretchType="NoStretch"/>

    <imageExpression

    class="net.sf.jasperreports.engine.JRRenderable">

    <[CDATA[com.cameleon.doc.DrawingEdge.getDrawingJasper($F{Drawing})]]>

    </imageExpression>

    </image>

• In the main report:
  • In the "report Inspector" tree, unfold "Scriptlets" branch and click on "REPORT". Complete "Scriptlet Class" by: "com.accesscommerce.cart.report.Scriptlet". (This updates the parameter "REPORT_SCRIPTLET".)
  • Create a variable called : "HeadingsCollection" and put the value "java.util.Collection" in its "Variable Class" parameter
  • Complete the field "Initial Value Expression" in the created variable’s parameters with : "new java.util.ArrayList()"
  • Before sub-report, in the band "Summary" of the page, add a label (static text) called : "BEGIN_TABLE_CONTENTS"
  • (This allows you to move the table of contents at the beginning of the report.)
  • Beware the field must have a height equal or greater than 14.

• Make it pass the variable "HeadingsCollection" as a parameter.
• Do the same for all sub-reports except the Table of Contents.

• In the band "Summary" of the page, add a label (static text) called:
• "BEGIN_TABLE_CONTENTS".
• Beware the field must have a height equal or greater than 14.
• Create a parameter called: "HeadingsCollection".
  • This is used to retrieve the value of the variable passed as a parameter of the sub-report by the parent report. Do the same for all sub-reports except the Table of Contents.
  • Create a variable called: "HeadingsCollection" and put the value "java.util.Collection" in its "Variable Class" parameter.
  • Complete the fields "Initial Value Expression" and "Variable Expression" in the created variable parameters with: "$P{HeadingsCollection}".
  • In the band "Summary" of the page, include in the display order pages you want to see before the table of contents.
• (i.e.: You want: Page 1: Cover Page, Page 2: Cover Letter.)
• Then add after them the Table of contents sub-report.

• In "connection type" put: "use a data source expression".
  • In "data source expression" put: "new net.sf.jasperreports.engine.data.JRBeanCollectionDataSource($V{HeadingsCollection

    })".

• Make it pass the variable "HeadingsCollection" as a parameter.

• Create a field called: "headingType" and is type is Integer.
• Create a field called: "headingText" and is type is String.
• Create a field called: "reference" and is type is String.
• Create a field called: "pageIndex" and is type is Integer.
  • Create a variable called: "Page" and is type is Integer. Put on "Variable Expression" : "new Integer($F{pageIndex}.intValue())"
  • To create a standard table of contents, re-use the example file Proposal_Summary.jrxml. You will have the first two title’s levels of Table of contents with the right conditions.

All titles must be owned or included in the sub-report which belongs to the "Details" section of the sub-report with the "Summary" section which is located in the sub-report "Table of Contents".

• Draw a line under the title that you want to see in the table of contents.
• For this line, complete the field "Print when expression" with the value: "$P{REPORT_SCRIPTLET}.addHeading("Section_name", "Level_of_title_in_Table_of_contents”, "Text_to_display")"

i.e. : $P{REPORT_SCRIPTLET}.addHeading("HealthQuote", "1","Your personalized health quote".

Or with a variable :

$P{REPORT_SCRIPTLET}.addHeading("HealthQuote ", "2",$F{TitleOffer})

• The created line does not appear in the generation of report.

• CPQ has the capability to send a locale to the report generator at runtime in order to use it as the locale of the generated report.
• The setup is made through the property locales of the report service that contains one value for a given locale or the value . One locales parameter has to be declared per locale to be made available.
  • The following input are accepted:
  • service.MyProposal.locales=fr-FR,en-US,nl-NL
  • service.MyProposal.locales.FR.fr-FR=Français
  • service.MyProposal.locales.US.fr-FR=French
  • service.MyProposal.locales.FR.en-US=Anglais
  • service.MyProposal.locales.US.en-US=English
  • service.MyProposal.locales.FR.nl-NL=Hollandais
  • service.MyProposal.locales.US.nl-NL=Nederland
• At runtime, if the locales parameter is defined, a new combo box is displayed in the report parameter view to display the locale choice (with translations defined in the service parameters), in order for the end-user to choose one.
  • If the chosen locale exists, it is set as a system parameter sent to the report generator:

    datas.addSystemParameter("REPORT_LOCALE", Locale.forLanguageTag

    (request.getParameter("localeChoice"));

The locale, if it exists, must also be saved in the parameter settings table.

• If the locales parameter is set to "Cart", the locale from the Quote will be sent to the report generator. - service.PROPOSAL.locales=Cart - Use Language connector (convertCountry & convertLanguage) to convert the cart language to a locale. - No need to display it in runtime parameter view.
  • During the design phase, if you want to personalize some fields from your report template, you have to declare a translation file per locale.
  • Path and name: reportPath + reportName + "/translations/translations_"

    +locale.toString()+ ".properties”

  • The "locale" portion of the translations file name needs to be: xx_XX
  • In each translation file, you have to declare each field for which you want to distinguish the locale. To do so, use the following syntax:
    • For instance in translations_fr_FR.properties:
      
      
• For instance in translations_en_US.properties:
  
  
• At runtime, if locales is used (Cart or list) in the cartServices.properties file:
  • CPQ will try to find a translation file corresponding to the locale
    • If found, CPQ send it to the report generator that applies the translation for the fields declared in the corresponding translation file.

• The setup is made through the property reportMultiLanguage=Yes of the report service
• Report services are declared in the file service.properties and can be overloaded from the XML WS file
• Each set of report and sub reports (one per language) must be stored in a dedicated subfolder named with the language ID.

• US (english) language
• …/US/proposal.jrxml
  • …./US/proposal_CoverLetter.jrxml
  • …
• FR (french) language
  • …/FR/proposal.jrxml
  • …/FR/proposal_CoverLetter.jrxml
  • …

If a Jasper report includes sub-reports, the report has to be completed with the following elements for the sub-report definition:

<subreportParameter name="REPORT_RESOURCE_BUNDLE">

<subreportParameterExpression><![CDATA[$P{REPORT_RESOURCE_BUNDLE}]]>

</subreportParameterExpression>

</subreportParameter>

This has to be repeated if the sub-report also has sub-reports.

The access rights matrix concerns all the elements of the quote header having the property "Access rights" set to "restricted". Each element is listed as a line in the matrix. The matrix properties are detailed in the table below:

Rights are cumulative. In case of contradictory settings, the rights ON will win over the rights OFF

The access rights matrix concerns all the elements of the quote spreadsheet having the property "Access rights" set to "restricted". Each element is listed as a line in the matrix. The matrix properties are detailed in the table below:

Rights are cumulative. In case of contradictory settings, the rights ON will win over the rights OFF