nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Remove current user from list box item

becool321

Hi Guys,

I'm trying to remove current user from approver list as seen from my datacapture.cfg code in file attachment.

Any suggestions, thanks.

Find more posts tagged with

Comments

ISCBorisB

Hi Guys,

I'm trying to remove current user from approver list as seen from my datacapture.cfg code in file attachment.

Any suggestions, thanks.

One obvious problem here is that you never call your "init" function. Modify like this:

<script><![CDATA[
IWEventRegistry.addFormHandler("onFormInit", init);
function init() {
. . .
}
]]></script>

Further, I do not think that you manipulate Options correctly. You use uninitiated approverList
Array in a loop as if it contains something, etc... If I were you, I would create new options array
that I need and use Item.setOptions() Method to actually set the new options.

Migrateduser

Hi Guys,

I'm trying to remove current user from approver list as seen from my datacapture.cfg code in file attachment.

Any suggestions, thanks.

Use options.length instead of approverItem.length.

[PHP]

function init() {
var approverItem = IWDatacapture.getItem("/Config/Approver");
var currentUser = IWDatacapture.getUser();
var options = approverItem.getOptions();

for(i=0; i if (options.value == currentUser)
approverItem.removeOption(i);
}
}

[/PHP]

becool321

Thanks Guys for suggestions. Tallgaard your recommendation was the final solution, thanks again.

becool321

Guys,

Previous solution is good but not great. This would require manually updating list. A better solution is for me to do this dynamically.

However I have tried datasource prior but was unsuccessful so I'm here again. I have 2 issues:

1. to get the name of the data source "Livesite Reviewers" from (function getDatasourceNames()) dynamically from list. Once I get datasource dynamically from list, I will hide this item from user and

2. to dynamically remove current user from this datasource list (function setDatasourceNamesToSelect(resultObj, returnParams)) as seen in my code (attached file). Tried removeOption here but didn't work.

Everything else I tried either break the code or I get no different result. Currently code works selecting datasource names then selecting name from list.

Your help is appreciated.

Rick Poulin

That approach sounds incredibly backwards. Why don't you instead copy the Livesite Reviewers code and write your own datasource that removes the current user and provides a list back to FormsPub that doesn't need client-side modification?

jbonifaci

If you want to take advantage of the datasource object and the OOTB datasource, there are a couple simple options to do what you are trying tod. So let's say you are calling your datasource like this:

 var datasourceObject = new IWDatasource();
 var datasourceMap = new IWMap();
 var contextMap    = new IWMap();
datasourceObject.executeDatasource("callBackFunctionNameGoesHere", "LiveSite Reviewers", datasourceMap, contextMap);

 callBackFunctionNameGoesHere(resultMap, contextMap)
 {
  var datasourceObject = new IWDatasource();
  datasourceObject.addOptionsToSelect(resultMap, "/Item/Name/Goes/Here");
 }

To modify this to remove the current user, you have 3 options:

1) At the end of the callback function, you can add code that retrieves "/Item/Name/Goes/Here", gets the item options array, removes the element you don't want (the one for the user) and then sets the options array with the new array that doesn't have that user.

2) Remove the current user from the resultMap object before you pass it to addOptionsToSelect.

3) Don't call addOptionsToSelect, just write your own code to take the resultMap and populate your item object. While building the item option array, simply skip over the current user while you are doing this.

All of these options should be fairly simple to do if you have any skill with javascript.

If you have a reusable function you can call for #1, I would recommend that. Otherwise, if you aren't a fan of reuse, just go with 2 or 3.

Let me know if you have any questions.
~Jeff

becool321

Thanks Jeff been away for a while working on other higher priority development tasks.

Anyway I have returned to complete this task. I have been using step 2 which I have made progress but I'm stuck again at line 77 which is giving me an undefined value. I have been able to remove current user in line 75 - 76, but having issue adding/setting options from line 77 onwards.

I have defined newOpt in line 68, so what is the issue and I'm following formapi manual on defining new options array.

I have attached my revised code, thanks for your help.

jbonifaci

Your function setOptionsToSelect is actually doing what I suggested as option #3 above. So if you are going to try to populate the options yourself, you don't want to call datasourceObj.addOptionsToSelect on line 43. So basically line 43 is overwriting everything you do in setOptionsToSelect.

Your code for setting the values looks ok, but there are a few things I would recommend for improving it:

1) You are changing currentUser to all uppercase, but not converting the actual value to upper before comparing. This is obviously bad and will result in a mismatch when the cases differ.

2) In your if/else in lines 72-79, if the current user is in the list, and is not the selected user, it will call addOption on line 80 with newOpt having a value of an empty array. Revise your code so that you only add the option when you actually have one to add.

3) Personally, I prefer to use addOptions. Just build your array of options and then when the array is complete, call .setOptions(OptionArray). I think this is much cleaner and doesn't require your call on line 57 to empty the item out.

4) If the object returned is an array, you don[t seem to be doing anything around checking for the current user (lines 83-96). If you always know it will be an IWMap object, I would suggest removing this section.

5) Do you know which datasource you want to call? Why are you loading the list of datasources? Is this just for testing? I would find it strange that you have a form where you would want the user to be able to select any datasource.

Let me know if this clears up your issue(s), or if you have any other questions.

~Jeff

becool321

Thanks Jeff for your suggestions.

I actually wanted to only list datasource "Livesite Reviewers" only. How do I get this list to load only without allowing user to select it and not have any other datasource choices?

I will hide list item (datasource list) from users so they will only pick approvers after datasource loads.

jbonifaci

There is no need for the datasource item if you don't want it. The only point of having such an item would be to have multiple selectable values for a user to pick.

If you are always calling the same datasource, simply configure your executeDatasource to pass that value, as I showed you before:

datasourceObject.executeDatasource("callBackFunctionNameGoesHere", "LiveSite Reviewers", datasourceMap, contextMap);

And if you want this to happen when the form loads, simply add a call to your setValueForDatasource function in your init function, instead of registering it to be called onItemChange:

function init()
{
 setValueForDatasource();
}

Obviously you need to change your function to not take any parameters and to remove the unnecessary if, but that is all you need to change to get it to call on load.

Let me know if you have any other questions.

~Jeff

becool321

Thanks Jeff, I got it working the way it should.

However, the select box for approver item is not wide enough and I can't seem to change the width so all data is showing for each approver.

Here is revised code in attachment. Your expertise/advice is requested again.

jbonifaci

Yeah, unfortunately the auto resizing doesn't seem to work in an initialize function that doesn't have any options.

Anyway, you should be able to get around this by including a single option (which will get overwritten anyway):

[HTML]

[/HTML]

Let me know if that works for you.

~Jeff

becool321

Thanks Jeff for your assistance in getting to final solution. I needed to include an option as you suggested.

This solution is for rpoulin, my "incredibly backwards approach" works and also for helping others with similar or related task.

Final code is in attachment.

Thanks to all who helped, Jeff I owe you a case of beer.

Cheers.

jbonifaci

Thanks Jeff for your assistance in getting to final solution. I needed to include an option as you suggested.

This solution is for rpoulin, my "incredibly backwards approach" works and also for helping others with similar or related task.

Final code is in attachment.

Thanks to all who helped, Jeff I owe you a case of beer.

Cheers.

My pleasure, glad to help.

Man, you don't know how many times people have promised me beers on DevNet. I have yet to collect on a single one, lol,