PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 02/19/2015 1:29 PM by  Peter O
Adding a New Form with Configuration Console
 1 Replies
You are not authorized to post a reply.
Author Messages
Herman Schultz
Tech SC
New Member
(1 points)
New Member

Send Message:

08/09/2013 12:17 PM
    Is this possible?  How?
    Peter O
    Systems Analyst
    Veteran Member
    (205 points)
    Veteran Member

    Send Message:

    02/19/2015 1:29 PM
    Hi Herman,

    Short Answer - No. Not possible, DEPENDING on what you mean by "adding" a new form.

    Long Answer-

    Forms are derived from a business class, so you cannot have a "Blank Form" (at least in Landmark versions 10.0 and 10.1.x) that is not tied to a business class.

    In config console, there's a bunch of forms that you CAN use and modify as a configuration for basic purposes, OR you can extend them for different purposes.

    Here's where Action Extensions and Action Overrides come into play.

    For example, we hijacked the "RequestNewPosition" and "RequestPositionUpdate" forms since our end users wouldn't be using the default functionality of those forms.

    We created an Action Override for those forms to modify what is minimally required when the Form is submitted and an action request is generated- this is the closest you'll get to a "blank form".
    We also created an action extension so that we could use a different Service and trigger a different action (service) than what the form is delivered with.

    The rest is what service you link the action (service) up to for use in IPA.
    So let's say we caused the form "RequestNewPosition" to call a custom action (service) "RequestRequisitionCreation".
    This would then Submit that form to call the flow associated with the Action "RequestRequisitionCreation". Obviously, there's a little more setup than this, but hopefully you get the picture.
    This would call our custom flow which would handle the job accordingly.

    In LPL it appears that for some reason the service is referred to as an "action" (i.e. - "request action process is RequestUpdateToPosition" or "action is RequestPositionUpdate").

    You are not authorized to post a reply.