跳到主要内容

FormGalleryDto

Where the ready-made form templates are served from, for browsing them and for submitting new ones.

NameTypeDescriptionNotes
pathStringThe path under domain that the gallery's own listing API is reached at. It is joined to domain by the client; the portal only relays the values from its configuration.[required] [example: /forms/templates] [nullable]
domainStringThe address of the gallery service, which is a service of the vendor rather than part of the portal. Every field of this object is empty on an installation that configures no gallery, and a client should then not offer the gallery at all.[required] [example: https://forms.example.com] [nullable]
extStringThe file extension to ask the gallery for, which decides which rendition of a template is downloaded when several are published.[required] [example: .docxf] [nullable]
uploadPathStringThe path used for submitting a form of one's own to the gallery, the counterpart of path for the upload side. The four upload fields are empty when the installation allows browsing but not submitting.[required] [example: /forms/upload] [nullable]
uploadDomainStringThe address the submission is sent to, which may differ from domain.[required] [example: https://upload.forms.example.com] [nullable]
uploadExtStringThe file extension a submitted form has to carry.[required] [example: .docxf] [nullable]
uploadDashboardStringThe page a person is sent to in order to follow up on a submission, joined to uploadDomain the same way as uploadPath.[required] [example: /dashboard/forms] [nullable]