Allow custom values in Import Mapping > Microflow to obtain object

When using custom Microflows in Import Mappings, only arguments from the import context (parent objects, values from the current node, import parameter) can be used as MF parameters. It would be very helpful to allow custom expressions and enums as arguments to make microflows better reusable

• e.g. create a microflow to obtain a Company Object as A) the actual company with all parameters filled, B) a reference to the company, with only the ID and the name filled
• e.g. create one microflow to create a PersonAttribute Object, and select the _type ENUM value as parameter, to not create a microflow for each ENUM type, i.e. personioToBirthdayvisibility, personioToEmploymentType, ... which are all just PersonAttribute Objects