Skip to Content
avatar image
Former Member

Will the new implementation of Local Language apply to Custom Compensation Statements?

We have implemented custom compensation statements for our Merit Cycle process. We are wondering if the new implementation of Local Language from the 2017 Q2 release will apply to custom compensation statements as well.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jun 16, 2017 at 03:35 PM

    Hello Toni.

    I doubt it would apply to custom statement automatically.

    Easiest way to test it is by generating statements as test. If you don't see this working then proceed as follows:

    If you are familiar with XSL then please add a new standard statement from SuccessStore, export this file, and open in a text editor of your choice.

    Once there look for following four Parameters(Starting with userLocale)

    Now perform an export of your custom statement template and check if these parameters appears there or not. If you can't find these there it means the new feature may not automatically work on custom statement.

    If you wish to update your statement you may involve your implementation partner or follow these steps on your own.


    Don't overwrite your existing custom statement. After you export make sure you save a backup before making any changes.

    Now, coming to updating custom statement. Copy these 4 parameters mentioned above into your custom statement after last <XSL: param name>

    Once done search for following code(xsl:decimal-format) in standard statement template.

    Copy these three lines in your custom statement.

    Once done, search for moneyFormat in your custom statement under tags xsl:value-of select and replace it with $userLocaleSpecificMoneyFormat, $userLocaleSpecificDecimalFormatter

    Something like this:

    <xsl:value-of select="format-number($lumpSum, $userLocaleSpecificMoneyFormat, $userLocaleSpecificDecimalFormatter)"/>

    Repeat for all moneyFormat fields.(hopefully developer used meaningful naming convention)

    Once done, try to import the statement and see if it imports. If it does it means no issues so far.

    Now, go back to editor and search for percentFormat and replace it with $userLocaleSpecificPercentFormat, $userLocaleSpecificDecimalFormatter

    Similarly repeat for amountFormat.

    Let me know if you face any issues.

    Also, may I request that you post such questions over here Customer Community



    Add comment
    10|10000 characters needed characters exceeded