Hi Rena,
You can try to use an image and change it based on a parameter.
Kind regards,
Julio.
Hi Ankitpur,
It is a long shot, but i believe the only way is creating a validation rule, with a regex for instance to avoid incorrect input and display error message.
Kind regards,
Julio.
Hi ashahbou,
Maybe something from TemplateVersionDao can help you with that.
Otherwise you can add another property with version= previous to query the form...
Regards,
Julio.
Hi Sean,
You can implement it by your own, and add the same action of the Maestro's default on change action: Translation.fetch(value) . Remember to use as a value the same stored in TM for each translation.
Kind regards,
Julio.
Hi Lin,
They are supported, but bear in mind EOL of Composer: https://docs.avoka.com/Support/EndOfLifePolicy.htm
Kind regards,
Julio.
Hi Skumar,
Maybe this link can be helpful: community.avoka.com/.../7130
We explain there how to use, does and don't, for external js resources.
Kind regards,
Julio.
Hi,
There's a removeProperty method/s within PropertyType entity.
Is it a client property?
Regards,
Julio.
Hi Alex,
You can delete an Organization and all its dependent entities (eg forms, submissions) from Transact Manager will be deleted. Do consider this carefully as this cannot be undone and will permanently remove the Organization and its...
Hi Alex,
You can delete an Organization and all its dependent entities (eg forms, submissions) from Transact Manager will be deleted. Do consider this carefully as this cannot be undone and will permanently remove the Organization and its configurations. If possible, Organizations should be made inactive instead of deleted, especially if there have been submissions for any of their forms.
Regards,
Julio.
Mi Mark,
You can try to use TransformerFactory (Java allowed on fluent).
I guess you need the attributes to generate SAP headers on the payload. In your service you can create the xml payload as a template with parameters. Those parameters will...
Mi Mark,
You can try to use TransformerFactory (Java allowed on fluent).
I guess you need the attributes to generate SAP headers on the payload. In your service you can create the xml payload as a template with parameters. Those parameters will be the info you need to add on the template to create the payload to send to SAP. Your service will use the transformer to set the values of those parameters dynamically and get the payload instance to be sent.
I hope this can help.
Kind regards,
Julio.
PS. Also if you are used to velocity, VelTemplate (from Avoka SDK) is helpful to generate repetitions, conditionals to add a node or not, etc...
Hi Lin,
I think you can create a custom component in your project library with that settings, and use it instead of the default one.
Kind regards,
Julio.
Register to ask a question and access to more content.