When using a percent field as token, the system is resolving only the value, or the number inputted into the percent field, but the value is not resolved with the percent sign(%).
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Add a percent field as a token;
- Input some value into this percent field;
- Now generate a new Offer Letter and use the token related to this field;
- Notice that the percent sign is not resolved alongside the value, differently from what we see on the currency fields:
This is due to the percentage field design, and how the values are stored on the system, which affects the token when resolved.
Although the percent and the currency field look like they work in a similar way, on the design of the functionality they are very different.
Currency: The currency field has a relation with the currency and the locale, which will be applied to the value when resolving the token value. Depending on the currency being used the sign must change, and having that to be done manually by the users could cause confusion and open the room for possible mistakes.
Percent: When resolving the percent field, as there are no variations, like what we see on the currency, that the sign may vary according to the currency in use, there is no need for the system to identify and auto-populate the value, so the functionality of auto-populating the sign right next to the value was never implemented into the percent field. Another reason why, is that the percent field values are stored as the number (e.g. "12.0") and do not have the % sign concatenated to it, which means that when resolving the percent will not be part of the value, so when using it in offers we must add the value into the offer template.
percent, offer, token, letter, resolve, sign, resolve , KBA , LOD-SF-RCM-CAO , Candidate Offers, Offer Letters , Problem