I don't think this is possible exclusively through the action processor but you can probably do this through an API call triggered by the AP. I tend to use PowerShell, but I understand from IFS that you could likely use your language of choice in your scripts.I cannot provide a polished script because we do not populate custom fields in this way. Someone like @MennovH might be able to give you a more elegant way of doing it but here is an example that might give you a spring board.Maybe a simple trigger like...strPowerShellAPI = [[PowerShell -ExecutionPolicy Bypass -Command "cd 'F:\Axios\WindowsPowerShell\APIScripts\'; & '.\]]{ [[ Field concatenate on commit ]], [[ ACT_TYPE_SC == "COMMIT" and EVENT_TYPE == "t"]], strPowerShellAPI .. "[INSERT SCRIPT NAME]' -myEventId $EVENT_ID -myEnvironment " .. env, "stop"},Note: I use the environment to dynamically fetch the environment credentials from the base config, but you could hardcode if you aren't confident using that method. Then a scr
I don't think this is possible at the moment because the customiser doesn't accept ‘NOT EQUAL’ (as below) or conditional AND/OR expressions$W("VISIBILITY-TEST")!="WANT2HIDE" If you want to show a field on 3 of 4 options then I think you have you create the hidden field 3 times. Adding specific, positive visibility expressions to each. It would probably make a great feature request though. It would get my vote.
I should have read this thread first.
We found away around this issue earlier today. If you remove the user’s permission to edit their own homepage then it forces the new layout. After some testing, it is limited to users that log in whilst the permissions are absent.
Its not possible at the moment but it is an existing idea. Might be worth an upvote.Visibility Expressions can reference System Fields | IFS Community
We try to maintain an evergreen approach, dipping no more that 2 minor version behind the current unless we find any showstoppers in testing.Its likely we will jump on 11.6 as soon as it gets released as it is likely to close an open risk we have relating to legacy email protocols and brings us closer to our WCAG AA goal. Subject to testing of course.
Try an Item Relation mapper.
This would likely be fixed by something like…. You are effectively narrowing the field for the search. The ‘Record to Update’ wants to return a single entity for you to update.
When searching for relationships, you will need to search for the item and relationship combination. Try using this +(plus) symbol for your additional criteria. This should appear outside of your item search criteria.This will enable you to search for a relation type of x on y item/ asset. So from your example, a relationship of ‘CONNECTED TO’ on item ‘IT-OP-016-L’
Nothing sensitive (that I can think of). When I say legacy, it would probably be more accurate to say basic authentication protocols (see the MS Learn topic for details). We have a risk open relating to whether MS will decide to turn SMTP (which I understand underpins SmartMail) off on tenants,. Probably more of a ‘when’ as this has been in the pipeline for a few years now.Deprecation of Basic authentication in Exchange Online | Microsoft LearnIFS have already replaced IMAP with modern authentication in the ETM using Graph. My fingers are crossed to see similar replacements for SMTP in the 11.6 release notes.
We were working on this task yesterday. I found that I got that and similar errors when my JSON (or possible XML if you are using it) has syntax errors or where the value I was trying to use did not already exist in the system for that event type. We found that this worked for us….Note: we were passing the $seedId variable in as an integer.{ "eventTypeEnum": "NORMALTASK", "remarks": "My Task Description", "importProfileId": 1, "taskLinkReasonId": 1, "taskSeedEventId": $seedId, "affectedUser": { "resolvingParameters": [ { "parameterName": "shortCode", "parameterValue": "$affectedUser" } ] }, "itemA": { "resolvingParameters": [ { "parameterName": "shortCode", "parameterValue": "$itemA" } ] }, "category": { "resolvingParameters": [
Correct, the taskSeedEventId is the parentEventId.I’m not very good with lua to be honest but it looks right to me. Maybe someone with more experience in the language can take a look.
Maybe [SM_ACTIONING_USR_N]?
Reordering catalogue links ‘should’ be drag and drop exercise (as you say) with the catalogue link reasons being subject to sort order fields in their config.But…. I do remember uncovering an issue when testing one of the versions in the 11.4 series that produced similar behaviour and prevented new links from being added. I pinpointed it to having system fields dragged into the custom field area in the customiser (specifically, itemB).It might be worth a try. I will give it go in our test environment next time I am in there.
We had to use a holding item called “Please Select….” as a workaround here. The downside being that it does class as an item and so will not flag as a mandatory field if an end user does not change it.
We are proceeding with out test environment very soon.It is good to see the continued development of the promotion tool. Combined with the Process Designer improvements in 11.5, this will save us a lot of time (and human error) in migrating new services to production.I’m also excited by the prospect of search tags on offerings. Especially if we can configure the feature to allow business areas to self-serve them maintain them.How about you?
It might not be the most elegant solution but try this to stop the common junk inputs….add combinations as needed.\d{6}(?<!000000|111111|222222|333333|444444|555555|666666|777777|888888|999999|123456)
We are running with 11.5 but this might work for you.select item.id from item as item where item.product.productClass.shortCode = '[Item Product Class]' and item.shortCode !='[Item Shortcode]'
Credit going to Lukasz on the service desk for this one. Thanks muchly. This was a real head scratcher for us.from item as Item where Item.id in (select itemConfigA.item.id from item_config as itemConfigA where itemConfigA.configChar.id in (select itemConfigB.configChar.id from item_config as itemConfigB where itemConfigB.configChar.id = (select configChar.id from config_char as configChar where configChar.shortCode = '[Insert Characteristic Shortcode]')))
Will do. Thanks.
I have never been able to search on a null value on the ETM, however there is a possible workaround.In my trials, I tend to find that the search lists are in id order and the ‘unknown-’ record is first. If this is the same for you then you could use something similar to the screen shot below.
I don't see this in ETM 1.5, but it does seem to be a new feature in ETM 1.6.
Thanks Caroline. So the ability to click on each update serves no purpose other than to drive aesthetics?
I thought you might like the idea that I submitted given the tags on this post.assystnet access to additional affected users | IFS Community An alternative might be a multi-select lookup using location data instead of affected user? Possibly accompanied by a script that populates the additional affected users of a ticket based off the selected site contact details?
We have use API to generate tasks in a couple of processes. I have adapted my code to include a foreach element that cycles through events in an object. You might event be able to populate the object array from a .csv or .xlsx file using Get-Content. It might do what you want it to...Function Set-JsonBody($eventType,$description,$importProfile,$affectedUser,$itemA,$category){ $myJsonConstruct = @"{ "eventTypeEnum": "$eventType", "remarks": "$description", "importProfileId": $importProfile, "affectedUser": { "resolvingParameters": [ { "parameterName": "shortCode", "parameterValue": "$affectedUser" }, { "parameterName": "CSGId", "parameterValue": "0" } ] }, "itemA": { "resolvingParameters": [ { "parameterName": "shortCode", "para
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
