Smart Fill changes
Smart Fill for Common Vacancy Fields
As explained in Using Smartfill on Campaign Vacancy Fields, we exclude some of the campaignForm values from being prefilled when smart fill succeeds. The reasons as to why they are ignored is explained in the recipe page.
HAPI Backend recently added support for more fields to be prefilled however they are still ignored because of the reasons listed in the recipe. Please refer to Allowlisting Vacancy Fields section in the recipe on how to allow prefilling of the newly supported backend fields.
Smart Fill for Products with Posting Requirements
Version 3.4 made the previously experimental changes publicly available for the product posting requirements.
We have now added the ability to prefill Product Posting Requirements form via Smart Fill.
End users will now see above the form a FILL IN WITH AI button.
ATS developers, to trigger the Smart Fill, refer to the Using Smart Fill on Channel Posting Requirements recipe.
Changes
The function createSuggestionOfPostingRequirements in campaign module with type CampaignServiceCreateSuggestionOfPostingRequirementsHandler has had arguments adjusted thus now accepts contractOrProductId: string or number instead of just contractId: string | number however there is now a fourth argument to indicate that the ID you are passing belongs to the product.
The type CampaignPostingRequirementsSuggestionCreateRequest and type CampaignPostingRequirementsSuggestionsGetRequestResponse have been changed so that it also supports product_id when request is done for a product.
Smart Fill Button Improvements
These are the changes made to Smart Fill button based on received feedback from ATSs:
- Changed the "[AI]" text to a Sparkles icon
- Changed the button's text from "Smart Fill" to "Fill in with AI"
Translations added
| Key | "en" value | "de" value | "nl" value | "fr" value |
|---|---|---|---|---|
| campaign.smartfill.button | Fill in with AI | Mit KI ausfüllen | Invullen met AI | Remplir avec l'IA |