Though I have filed feature request on custom-attribute support in the new javascript engine for over half a year,  I am not aware of any such implementatation in the latest device agent release.

Thank you Raymond. I will contact support to find out if there is any progress. I consider it as a common behaviour.

Hi Zdenek, why do you explicit want to use Javascript? 

And who is "the user" is it the admin user or phone user (i think you mean the phone user)?

1. You can create the custom attribute in the console in general, so no java script needed here

2. If "somehow the IP is entered and stored in an xml file" there's no java script in the console needed (don't know what you use for that)

3. The console reads the value from the xml by itself into the custom attributes if configured - no javascript needed

4. You can access the custom attribute (for your samples it will be possible) with the legacy scipting.

Hi, Rafael, let me explain.

A customer requests a bulk change of IP addresses via a script. He has Zebra devices that allow to create an xml file capable of setting the IP address on the device. He is able to run this xml via the mxconfig command.

Your Java Script has the ability to create such a file. I am looking for a source of IP addresses, such source should be custom attributes.

So, if i now understood correctly:

You want a list of possible IP-addresses stored in custom attributes (centrally filled one time for all devices which is no problem but only one IP each or you have to work on a string (split etc.)) and then write that into an xml on the device and use one of that for the device as the new ip.

Is that correct understood?

Hello Rafael,

yes, excactly, you are correct. And you are also correct that storing atrributes per device is not a problem.  The problem is to use stored IP and newly setup each device by a script. I cannot find any way, so I am trying to use the functionality of Zebra (StageNow, by using xml. This csp profile is called Wi-Fi Manager and can by applied by mxconfig command)

Hello, for your information, reference number of this feature request is MC-134999.

Wouldn't it be maybe the same (but not as comfortable) if you just would provide an xml file to the device (with file sync rule or via package) with this data in and this can be read via javascript i think. Or I'm wrong here now?

Rafael, you're absolutely right. XML could be generated externally and uploaded using file synchronization for example. But the customer insists on the Mobicontrol scripting language. He knows that MobiControl has this potential and wants to use it. It is natural for JavaScript to work with variables, and a custom attribute is a variable.