Do you guys think a none technical person can use this feature (Low code/No Code)? I am providing you my honest openion as a Developer and a partner who has worked on many clients and many different projects and requirements, this is NOT a good solution. It is too complex for a none technical user to deal with JSON arrays and objects and its TOO boring for a technical person to work in this fasion!! Can you imagine how hard it is to trouble-shoot this when something is not working. I have a feeling that ServiceNow is moving toward a wrong direction with all these NEW changes!! Guess what happened to BMC when they ignored the partners and customers?
I personally like UI Builder (I am a technical person) but I know a lot of people think it is certainly too complex for citizen developers. It is certainly far more advanced than something like service portal designer or perhaps even Studio IDE. For me UI Builder feels quite visually logical which is why I like it - but if you simply know how to code then it's not necessarily useful, visual aspect alone doesn't justify its existence. I'd say UI Builder is too complex for those not interested in advancing beyond low-code/no-code and so not a good solution for ServiceNow to have, but perhaps there will be improvements in the future to make it more accessible to citizen developers.
Finally another person calling out SN's poor direction. As a senior consultant/dev, this app is infuriating to use and develop with and is far too complex for everyday industry SN devs which are not generally developers but ex support people coming up through the ranks. The amount of time trying to implement basic things is beyond a joke, and I will be advising customers never to use it due to the dev costs alone. And let's not mention the countless breaking and loading issues.
This might be a dumb question, but would it be possible to use the Function feature to bypass the Client Script here? e.g. CONCAT("dynamicuser^state=",@state.filter_state)? Or is a client state variable unable to access another client state variable unless the api.SetState() script is used?
Similar to building web components? Who exactly is this UI builder for because it's clearly not your average SN dev. SN knows about the real resource problem the industry faces, so it decides to create some overly complex application making dev costs more expensive and even harder to find resources. Unreal. Most don't even know basic javascript and SN expects them to understand this, JSON and web components? An Next Experience alright.
Do you guys think a none technical person can use this feature (Low code/No Code)? I am providing you my honest openion as a Developer and a partner who has worked on many clients and many different projects and requirements, this is NOT a good solution. It is too complex for a none technical user to deal with JSON arrays and objects and its TOO boring for a technical person to work in this fasion!! Can you imagine how hard it is to trouble-shoot this when something is not working. I have a feeling that ServiceNow is moving toward a wrong direction with all these NEW changes!! Guess what happened to BMC when they ignored the partners and customers?
I personally like UI Builder (I am a technical person) but I know a lot of people think it is certainly too complex for citizen developers. It is certainly far more advanced than something like service portal designer or perhaps even Studio IDE. For me UI Builder feels quite visually logical which is why I like it - but if you simply know how to code then it's not necessarily useful, visual aspect alone doesn't justify its existence. I'd say UI Builder is too complex for those not interested in advancing beyond low-code/no-code and so not a good solution for ServiceNow to have, but perhaps there will be improvements in the future to make it more accessible to citizen developers.
Finally another person calling out SN's poor direction. As a senior consultant/dev, this app is infuriating to use and develop with and is far too complex for everyday industry SN devs which are not generally developers but ex support people coming up through the ranks. The amount of time trying to implement basic things is beyond a joke, and I will be advising customers never to use it due to the dev costs alone. And let's not mention the countless breaking and loading issues.
This might be a dumb question, but would it be possible to use the Function feature to bypass the Client Script here? e.g. CONCAT("dynamicuser^state=",@state.filter_state)? Or is a client state variable unable to access another client state variable unless the api.SetState() script is used?
If we open a record to be shown - form fields , how do we have the button action added to save what is edited ?
+1
Similar to building web components? Who exactly is this UI builder for because it's clearly not your average SN dev. SN knows about the real resource problem the industry faces, so it decides to create some overly complex application making dev costs more expensive and even harder to find resources. Unreal. Most don't even know basic javascript and SN expects them to understand this, JSON and web components? An Next Experience alright.
Could we assign the already existing scripts such as UI Action and Script Includes to these buttons? Thanks