Validation on the value entered for the attribute-based LOV

Hello

I use R12 and created an integrator based on a Table based on a table of seedlings open interface. I use an approach that does not involve PLSQL since the Integrator is based on a Table on a table of seedlings open interface and I have so defined it an importer to call a simultaneous program seeded import. I also put in place a LOV component on one of the attributes in the interface.

My question is, if in the spreadsheet, the user double-click in the cell LOV to extract, and then select a value (for example if they are in copying and pasting quite a few records if they manually type a value) and the value you entered don't is not one who belongs to a group of data from the LOV, this would raise a validation error when loading?

In this scenario, I would LOV to serve as a validation check to ensure that users can choose only one value that would be in the LOV, even if they have not actually open the popup LOV and selected a value there. I have some research which I would probably need to validate the data against and because my approach is purely a non-PLSQL that I think the best way to achieve this.

Appreciate your help as always

Concerning

Not to worry, I think I answered my own question by developing a little proof of concept.

As expected, you can enter values that are part of the DataSet LOV. Enter any other value will highlight the line as an error line asking the user to enter a valid value.

Thank you

Tags: Oracle Applications

Similar Questions

  • How to pass the value entered for the parameter IN a function

    Hello
    I'm new to pl/sql programming.
    The function below is used inside a package and the package is called in visual studio.
    The function uses the input parameters 2.
    Out what "in_report_parameter_id" value comes through the application of service job processor.
    The second IN the parameter values are hard coded into the function.
    I am not able to understand this.
    If the values are hard coded, how to ensure that only the hard coded values are the right ones?
    Please could someone explain?
    I don't really have good idea on how to move the INPUT parameter to the function or procedure
    Is there any nice document that could give me good understanding about what are the ways or types we could transmit values to the input in the subprogrammes parameter?

    Thanks in advance.

    CREATE OR REPLACE FUNCTION get_class_text_str
    (
         in_report_parameter_id IN NUMBER,
         in_which                IN VARCHAR2 DEFAULT 'SELECT'
    )
    RETURN VARCHAR2
    IS
             end_text            VARCHAR2 (50)   := ''; 
             my_class_text_str  VARCHAR2(10000) := '';
             my_class_value_str VARCHAR2(10000) := '';
     
         CURSOR class_text(c_1_text VARCHAR2, c_2_text VARCHAR2) IS
         SELECT c_1_text || report_parameters.report_parameter_value 
                               || c_2_text
                               || report_parameters.report_parameter_value 
                               || '" '
          FROM report_parameters
         WHERE report_parameters.report_parameter_id     = 3690
           AND report_parameters.report_parameter_group  = 'CLASS'
           AND report_parameters.report_parameter_name   = 'CLASS'
     GROUP BY report_parameters.report_parameter_value
     ORDER BY CAST(report_parameters.report_parameter_value AS NUMBER);
     
    BEGIN
    
         IF (in_which = 'SUM') THEN     
      
              OPEN class_text ( 'SUM(NVL("Class ', '", 0)) "Class ' );
        
         ELSIF (in_which = 'PERC')THEN
      
              OPEN class_text ( 'ROUND((("Class ', '" / "Total") * 100), 2) "Class ' );
              end_text := ', DECODE("Total", -1, 0, 100) "Total" ';
        
         ELSE
      
              OPEN class_text ( 'SUM(DECODE(bin_id, ', ', bin_value, 0)) "Class ' );
        
         END IF;
     
         LOOP
              FETCH class_text INTO my_class_value_str;
              EXIT WHEN class_text%NOTFOUND;
     
              my_class_text_str := my_class_text_str || ', ' || my_class_value_str;
         END LOOP;
     
         CLOSE class_text;
      
         my_class_text_str := my_class_text_str || end_text;
     
         RETURN my_class_text_str;
         
    END get_class_text_str;
    /
    Published by: user10641405 on November 19, 2009 08:16

    Published by: user10641405 on November 19, 2009 08:30

    This is not a conception I would use, but should work if coded correctly. I would probably create a reference text cursor query and use a fetch of open and close.

    You have 2 input parameters, in_report_parameter_id and in_which. I could not find where in_report_parameter_id has been used in the program, but the value passed to in_which is used in the logic of the FI to decide on opening the cursor. After the cursor is opened lines are to be read and possibly the cursor is closed.

    The in_which values are compared to the are hard-coded. It is the programming interface to ensure that the values are the values and the measures taken are also correct. Your program is assuming that if the first 2 values are not met the third listed is the one you want.

    To pass values of entry in a procedure you simply provide the values as a literal or something like variable in the call,

    whatever := get_class_text_str(1,'SELECT');
    
  • Validation of the attribute levels

    Hello

    I need to perform validation levels attribute between these two fields of type numbers, when the user tab in both areas if size is higher then its size fires and displays a message on the field from waist, well want to tell me how to do this?

    JDeveloper 11.1.1.6.0

    validation.png

    Kind regards

    Peyrot

    Take a look at:

    http://sundarakrishna.blogspot.com/2013/11/ADF-entity-object-entity-level-and.html

  • How to retrieve the value of the attribute-based

    Hello
    I save our file XML in a clob field.
    The contend of the XML file is as below
    < Reports >
    "< report Type = 'USE' Title = 'USE report' Link="-1-2010-11-2-0-39-48-750 ' UUTResult = 'Fail' StepCount '69' = >
    < prop Name = 'USE' Type = "Obj" TypeName = "USE" Flags = "0 x 0" >
    < prop Name = "Serial number" Type = "String" Flags = "0 x 0" >
    < value > 20302884 < / value >
    < / prop >
    < prop Name = "UUTLoopIndex" Type = "Number" Flags = "0 x 0" >
    < value > 2 < / value >
    < / prop >
    < prop Name = "CriticalFailureStack" Type = "Array" LBound = HBound "[0]" = "[1]" ElementType = "Obj" Flags = "0 x 0" >
    < ArrayElementPrototype Type = "Obj" TypeName = "NI_CriticalFailureStackEntry" Flags = "0 x 0" >
    < prop Name = "StepName" Type = "String" Flags = "0 x 0" >
    < value > < / value >
    < / prop >
    < prop Name = "SequenceName" Type = "String" Flags = "0 x 0" >
    < value > < / value >
    < / prop >
    < prop Name = "SequenceFileName" Type = "String" Flags = "0 x 0" >
    < value > < / value >
    < / prop >
    < prop Name = "Result identifier" Type = "Number" Flags = "0 x 0" >
    < value > 0 < / value >
    < / prop >
    < / ArrayElementPrototype >
    < value ID "[0]" = >
    < prop Type = "Obj" TypeName = "* NI_CriticalFailureStackEntry *" Flags = "0 x 0" > ""
    < prop Name = "StepName" Type = "String" Flags = "0 x 0" >
    < Value >pre-program test< / value >
    < / prop >
    < prop Name = "SequenceName" Type = "String" Flags = "0 x 0" >
    < value > MainSequence < / value >
    < / prop >
    < prop Name = "SequenceFileName" Type = "String" Flags = "0 x 0" >
    < value > Challenger_Phase1.seq < / value >
    < / prop >
    < prop Name = "Result identifier" Type = "Number" Flags = "0 x 0" >
    < value > 368 < / value >
    < / prop >
    < / prop >
    < / value >
    < value ID "[1]" = >
    < prop Type = "Obj" TypeName = "* NI_CriticalFailureStackEntry *" Flags = "0 x 0" > ""
    < prop Name = "StepName" Type = "String" Flags = "0 x 0" >
    < Value >regulator LogicReg< / value >
    < / prop >
    < prop Name = "SequenceName" Type = "String" Flags = "0 x 0" >
    < value > pre-program test < / value >
    < / prop >
    < prop Name = "SequenceFileName" Type = "String" Flags = "0 x 0" >
    < value > Challenger_Phase1.seq < / value >
    < / prop >
    < prop Name = "Result identifier" Type = "Number" Flags = "0 x 0" >
    < value > 371 < / value >
    < / prop >
    < / prop >
    < / value >
    < / prop >
    < / prop >
    < / report >
    < / Reports >



    Can someone guide me how can I retrieve the value of the Prop Name = "StepName", i.e. "Before the program tests" and "LogicReg regulator", which is 1 level under the TypeName = "NI_CriticalFailureStackEntry." I extracted the part of XML code below

    < prop Type = "Obj" TypeName = "NI_CriticalFailureStackEntry" Flags = "0 x 0" >
    < prop Name = "StepName" Type = "String" Flags = "0 x 0" >
    < value > pre-program test < / value >
    < / prop >
    and
    < prop Type = "Obj" TypeName = "NI_CriticalFailureStackEntry" Flags = "0 x 0" >
    < prop Name = "StepName" Type = "String" Flags = "0 x 0" >
    Regulator LogicReg < value > < / value >
    < / prop >


    Thank you

    Vincent

    PJ * wrote:
    I save our file XML in a clob field.

    If you still have the choice, you should consider storing XML data in XMLType column.

    For the moment, assume that the XML data resides in the CLOB SAMPLE_TABLE column. DOC:

    You can use XMLTable to break a sequence of XML elements in columns and relational rows:

    SQL> select x.*
      2  from sample_table t,
      3       xmltable(
      4        '//Prop[@TypeName="NI_CriticalFailureStackEntry"]/Prop[@Name="StepName"]'
      5        passing xmltype(t.doc)
      6        columns num for ordinality,
      7                val varchar2(100) path 'Value'
      8       ) x
      9  ;
    
           NUM VAL
    ---------- -----------------------------------
             1 Pre-program tests
             2 Regulator LogicReg
     
    

    XMLQuery or to extract it as a string:

    SQL> select xmlquery(
      2          'string-join(//Prop[@TypeName="NI_CriticalFailureStackEntry"]/Prop[@Name="StepName"], "|")'
      3          passing xmltype(t.doc)
      4          returning content
      5         ).getstringval() as "RESULT"
      6  from sample_table t
      7  ;
    
    RESULT
    ----------------------------------------------
    Pre-program tests|Regulator LogicReg
     
    
  • How to disable the warning of validation on the calculation (read-only) field in the table

    Is it possible to add a line in a calculation script (JavaScript) that prevents a dialog box of a calculation field validation?

    Scenario:

    • Working with fields in a table inserted.
    • In each line, I have a couple of fields that the user has entered. These fields have a Validation model has allowed that the user must enter the data correctly.
    • There is a calculated field based on the data entered by the users. It is this field that throws a warning dialog box "the value entered for Total_Row1 is not valid. "To ignore the validations for Total_Row1, click on ignore.

    Even if I turn off the Model Validation on fields used for the calculation of the warning dialog box always appears. So, it seems to be isolated in the field of computing.

    The calculation area displays the time and I got it originally set as a Date/time field, but also tried to use a text field (as the calculation should appear as 0:45 for 45 minutes in this area).

    I have a suspicion that the warning appears only because I used an array for formatting fields, as I used similar validation profiles and other calculation fields and see not the message when the fields do not appear inside the table.

    I think of easier workaround would be to disable validation for this particular calculation field, but I have no idea how the script that. Any help appreciated lot.

    CARI

    I discovered the problem.  In a word: it was a mistake by naming the fields.

    • I have fields named with line numbers in the field name (for example FieldName_Row1).
    • and fields calls with FieldName_Row1.formattedVallue must have triggered some confusion.

    As soon as I removed the word 'Row' of file names, the question of the warning dialog validation mystery Adobe Acrobat for the calculation field have disappeared.

    Ago about 3-4 hours of my life that I won't be back... ha - ha but if someone else has the problem, I thought I better share my discoveries

  • EO validaitions, dependence of the attribute

    Hello

    I use Jdev12c.

    I put a few commits in the OE, for example. 0 < = Attrib1 < Attrib2. Now, I have a form with these two attributes. Initially, I set values that are valid as Attrib1 = 20 and attrib2 = 40 and press OK. He committed. I open the form to change the values and put Attrib1 = 50 and Attrib2 = 80. Now if I press OK, the Validation fails. It seems he compares Attrib1 = value attrib2 = value 40 50.

    Should what steps I follow to get ride of this problem.

    Thank you!

    Validation of the attribute may not work here. You must implement a validation that validates the entire OS.

    Timo

  • Different behaviors in MAX vs LabVIEW when writing the attribute IMAQdx GigE

    Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

    However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

    I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

    I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

    Any help will be appreciated.

    AnthonV wrote:

    Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

    However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

    I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

    I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

    Any help will be appreciated.

    Hi AnthonV,

    "Weird" is a good way to describe the Spyder3 when it comes to the GigE Vision/GenICam interface (as opposed to the Dalsa driver that communicates using custom commands via ethernet camera series)...

    The Spyder3 has many questions focused on the calendar. It is possible that the time between the opening of the camera and the setting of this function is different by MAX vs your code in LabVIEW. In addition, there are some cases where MAX will be deletes the error to display. Ignoring the error indicated vs you see the feature to take effect in both cases?

    The base between MAX and LabVIEW behavior is the same. In both cases when you open the unit all parameters are responsible for our camera file that has the registered device settings. This file is created the first time that you open the unit and are updated every time you click on save to MAX or call an API function to save the settings. In any case, I know that the Spyder3 has various questions backup/restore the settings of our camera files.

    I suggest talking with Dalsa on the issues you are experiencing. They might be able to put up with a newer firmware that addresses some of these issues (we have worked with them in the past to identify several of them).

    Eric

  • validation error message is not displayed for an attribute as a list of value of the entry

    Hello world

    I use jdev 11.1.1.7.0

    In my application, I created an entity Obj and Obj employees base table.

    for the attribute JobId , I took the actions listed below:

    1. in the EO staff, I created a validation for this attribute and in some cases the error message returns (the error message is "the salary is not high"):

        /**
         * Validation method for JobId.
         */
        public boolean validateJobId(String jobid) {
    
    
            if (...) {
                return false;
            }
    
    
            if (...) {
                return false;
            }
    
    
            if (...) {
                return false;
            }
    
    
         
            return true;
        }
    

    2. employees Vo, I created a LOV for this attribute (the view accessor is JobsViewObj) and I display the attribute entry of text with a list of values.

    in the jspx page, I drag / drop this attribute as below:

              <af:inputListOfValues id="jobIdId"
                                    popupTitle="Search and Select: #{bindings.JobId.hints.label}"
                                    value="#{bindings.JobId.inputValue}"
                                    label="#{bindings.JobId.hints.label}"
                                    model="#{bindings.JobId.listOfValuesModel}"
                                    required="#{bindings.JobId.hints.mandatory}"
                                    columns="#{bindings.JobId.hints.displayWidth}"
                                    shortDesc="#{bindings.JobId.hints.tooltip}"
                                    autoSubmit="true">
                <f:validator binding="#{bindings.JobId.validator}"/>
              </af:inputListOfValues>
    

    I opened the popup and I select a line in the list and then I click Ok. After that, if the validation method (validateJobId) returns false, the error message ("the salary is not high") must be show to the user. but the error message does not appear. I don't understand why this is happening.

    Can anyone guide me on this problem?

    Concerning

    Habib

    Hello Dario,

    I just found this post: http://andrejusb.blogspot.nl/2013/12/workaround-for-infamous-bug-13626875.html that apply ExceptionMode = immediate adjustment to control the use of data in DataBindings.cpx, then the error message is displayed as I hope.

    Concerning

    Habib

  • Simulator Device.xml file has a tag with an attribute of memory, what are the optional values for this attribute of the os?

    In the Device.xml file, it starts with the tags of the os. Each os has a memory attribute. What are the optional values for the attribute memory?

    Can we really control the memory for the simulators?

    0x85000F03
    0x8C000F03
    0x87000F03
    0x84001503
    0x86001503
    0x04001507
    0x0F001507
    0x0C001404
    0x0D001404
    0x0E001404
    0x0D000D04
    0x16000D04
    0x05001504
    0x07001504
    

    These values refer to specific hardware configurations are simulated.  They should not be changed.

  • Getting the values for the attributes of the user in IOM

    Hello

    I have it here is the snippet of code that retrieves the values for all the attributes user OIM 11g. But this code returns the exception of null pointer for attributes with null values. I also put if condition to check for null pointer exception, but always the null value is thrown in the newspapers whenever this code snippet is executed in the event handler.

    Any thoughts?

    private Map getUser(String userKey) {
      Map users = new HashMap();
      User user = null;
      UserManager userManager = (UserManager) Platform
      .getService(UserManager.class);
      try {
      user = userManager.getDetails(userKey, null, false);
      logger.log(ODLLevel.FINE, "User: {0}",new Object[] { user });
    
      } catch (NoSuchUserException e) {
      logger.log(ODLLevel.ERROR, e.getMessage(), e);
      } catch (UserLookupException e) {
      logger.log(ODLLevel.ERROR, e.getMessage(), e);
      }
      Set AttrNames = user.getAttributeNames();
      logger.log(ODLLevel.FINE, "User Attributes: {0}",new Object[] { AttrNames });
    
      Iterator itr = AttrNames.iterator();
      while (itr.hasNext()) {
      try {
      String AttrNAme = itr.next().toString();
      logger.log(ODLLevel.FINE,"Current Attribute is : {0}::",new Object[]{AttrNAme});
      if( user.getAttribute(AttrNAme).toString()!=null && user.getAttribute(AttrNAme).toString().length()!=0){
      String AttrValue = user.getAttribute(AttrNAme).toString();
      logger.log(ODLLevel.FINE,"Attribute: {0} and Value: {1}",new Object[]{AttrNAme,AttrValue});
      users.put(AttrNAme, AttrValue);
      }
      } catch (Exception e) {
      logger.log(ODLLevel.ERROR, e.getMessage(), e);
      }
      }
      return users;
      }
    

    TIA

    A call to ToString on null will give you the exception. You should check that the value is not null before calling toString() on it.

    In addition, you must perform an additional control on the user object that you receive after your try catch block. If the user object is null, then there is no need to run code on the user object.

  • The value for the attribute Transient

    Hi Expert,

    I use JDeveloper 11.1.1.6.

    I want to put the value of pageflowscope value as for example #{pageFlowScope.userInfoBean.orgid} for a Transient attribute

    so I added a transitional attribute to the object View (VO), but in the value of the expression I put #{pageFlowScope.userInfoBean.orgid}

    This expression, it cannot be used.

    How can I do to set the value to the Transient attribute?

    Please advice me, really appreciate your help

    Thank you

    As someone has already said, this is not recommended (access to bean managed layer model), BUT try to put

    userInfoBean.orgid

    pageFlowScope first and then access this value as I told you

  • [ADF, JDev12.1.3] (How to set values for the attributes 1) to create a file and 2) committing to the database?

    Hallo,

    in my tables and forms (created from VO istances) there are some areas for which, insert and update, I calculate and set the value programmatically when a record is created or updated.

    In some cases, I put the necessary values using the 'CreateWithParams' in the workflow diagram...

    In some other ones, I associate an action, a bean, a created button drag-and - drop operation 'CreateWithParams' of the istance VO...

      public String cwpButton_action() {
        BindingContainer bindings = getBindings();
        OperationBinding operationBinding = bindings.getOperationBinding("CreateWithParams");
        // here I calculate and set the needed params
        // ...
        Object result = operationBinding.execute();
        if (!operationBinding.getErrors().isEmpty()) {
          return null;
        }
        return null;
      }
    

    And is ok if I can calculate the values for the attributes before a new record is created.

    But the approach that I have used to define the attributes (for new and updated records) whose value should be caluclated after the user has filled in the fields, before committing to the database?

    Thank you

    Federico

    Federico,

    Let me first tell you that our code is activity masking errors (the cache instead of working on them).

    1. If (! operationBinding.getErrors () .isEmpty ()) {}
    2. Returns a null value.
    3. }
    4. Returns a null value.

    This means that you do not check the errors at all. You must at least print a log with the error message, you receive, if you get one!

    To solve your problem, you override the method prepareForDML() of the entity or entities in question. You can calculate and set the necessary attributes until they get engaged in the doDML(). Do not use doDML() because it is too late in the life cycle.

    Timo

  • I have InDesign CS5.5 for 2 systems - my laptop crashed and I now have a new with Windows 8.1.  I downloaded the correct version of InDesign, but when I enter my l series #, the message reades # is valid, but the software cannot be raised

    I have InDesign CS5.5 for 2 systems - my laptop crashed and I now have a new with Windows 8.1.  I downloaded the correct version of InDesign, but when I enter my l series #, the message reades # is valid, but the software cannot be found on the system.  It seems that the program PageMaker 7 which is not on the new computer.  How can I load my InDesign CS5.5 on the new computer laptop?

    If you purchased InDesign CS5.5 as an upgrade then it looks like it's showing that you need to provide information about the old version where you improved since he found nothing that qualifies.  You must only choose the old version and serial number.  (I don't know anything about InDesign, nor how it might relate to PageMaker).

  • How to give the default value for an attribute in the OPA

    Hello

    I need a default attribute boolean to true at the beginning of the session of the OPA. I need to use it to control the visibility on some pages.

    Can someone please throw light on how to best implement this?

    Thank you.

    You have a few options (as always with the OPA!)

    If you use determinations of Web and that you have defined your own screens, then the easiest way is to define a default in the screen - you can either do a default static or dynamic based on an attribute is proved by a default rule.

    If you want a value by default when you debug without using screens, so you're better off just writing a rule to set the default value. It's kinda interesting with a Boolean value as you do not need to tell the value of the attribute OPA - it is inherent in the name of the attribute. For example, if you had a conclusion "control is visible" (with no = "true" or whatever it is) it would be set to 'control is visible' to 'true '. Set it to false, you simply need to type "control is not visible" - which actually (thanks to OPA assuming a 'subsidiary conclusion') defines "control is visible" to "false".

    You can then replace it in the debugger of via a screen issue (if you force the question).

    I don't know how it would work with server of determinations if you had a default value proved by a rule, but has also provided a value in the data - maybe someone else can clarify if the rule takes precedence over the input data? My usual approach is to try locally in OPM and see (using something like SOAPUI to integrate with the determinations OPA server web service). If that's the best way to implement this course (or indeed if using a default value of visibility control screen is best practice) is difficult for me to say - I am a relative beginner!

    Hope that helps a little...

  • Use workflow to enter the value of the attribute

    Hello, I have a workflow that turns off a virtual machine and it feeds and then turn it back on.  He sent an e-mail if it does not power the correctly.  Is it possible to insert the VM name which was the entrance of workflow in the value of the object or the contents of the email?

    Untitled.png

    Something like vmname % do not restart.

    Thank you, Zach.

    The correct is

    content = vm.name + " did not reboot";
    

    as it concatenates two strings - the 'name' of the object of type VirtualMachine property (the property type is string) with another string. Again, the result of this operation is a value of a string that is assigned to the 'content' attribute which is also of type string.

    This one

    content = vm + " did not reboot";
    

    is incorrect as it attempts to concatenate a VirtualMachine type object with a string. What should be the effect of this operation?

    You get this reference error because you have not added the input parameter "vm" tab within the script task . The code in a script task can run on attributes/parameters of the workflow that are explicitly referenced IN or OUT tab. those not referenced is simply not visible within the script task.

    When you select an existing tab attribute/setting, you are not redefining you mark this attribute or parameter as visible and accessible in the script task. When you select an existing attribute/parameter ON tab, you mark this attribute or parameter as keeping its value changes after leaving the script task. In your example, you included the attribute of "content" on the tabs IN and OUT , which means you can use it in Javascript code inside the scriptable job and that changes you make to it (setting the new vm.name + 'is off') updates the value of real content and will not be lost after leaving the task scriptable element.

Maybe you are looking for