Hello Amit, Support confirmed that the problem was in apache configuration file: "The configuration file for the apache need to be change to give proper file permission to a specific file path (the one that contains the xsl used within that workflow). Unfortunately, since this patch/configuration change is done at the server level, we do not have access to it. I only know the configuration change was needed to have access to the following folder: /usr/local/neolane/nl6/datakit/xtk/fra/xsl"Thank ...

Hello Florent,After opening three support tickets, support applied yesterday a patch on my platform. For now I don’t have more details about the applied patch. It is working fine now. Adobe Campaign Support team said on 14/02/2017: “The permanent fix has been added to the latest build that is currently being evaluated by Adobe Quality Assurance team right now. Once verified and the build is release, you would need to upgrade your environment to get the permanent fix.”Best regards,Nicoleta

Hello Florent,I'm still working with support on this. As soon as I'll have a solution I'll post it. Regards,Nicoleta

Amit_Kumar wrote... Hi Nicoleta, it looks like this file is not allowed from the apache server. please hack your firewall settings are apache config for prod for .xsl type files? Regards, Amit Hello Amit, Thank you for your answer.You are saying that I should look in apache config file to see if .xsl is well configurated?I also should ask Adobe support to check firewall settings for .xls, as all the platform are hosted at Adobe? Best regards,Nicoleta

Thomas Boucher wrote... OK so you should ask the technical administrator of your platform to enable it (it is not started by default because not everyone uses Inbound Interaction): as explained in the documentation link I pasted above, the "autoStart" should be set to "true" in the configuration file of your instance. Typically in config-.xml, simply search for the "interactiond" section and change the autoStart value: After a restart, new inbound interactions should be inserted in the DB. Best...

fleltuerto wrote... Hello Nicoleta, Ok I see. This is unfortunately normal behavior. While the auto-detect option can in some cases detect datetime columns, other types of columns are always recognized as strings, and it is up to you to modify each column manually so that it matches the correct data type and it is processed as you need when the workflow is executed. Basically, what this option does is only detecting the columns of the sample file and general file formating such as separating cha...

Anushia V wrote... Hi Nicolletta, I am not able to see interactions@[platform-name] on the processes list. Does it mean there is something missing in configurations? Thanks, Anushia I’m sorry I cannot help you with this. I don’t know why.

Anushia V wrote... nicolletta wrote... Have you checked your “interactiond" logs also? Do we have access to see interaction logs? I see adobe campaign console error - "No key defined for element 'interaction' (query on a document of type 'Interactions (nms:interaction)') Thanks! Normally in “Home” –> “Monitoring” à Process list à interactiond@platform_name

Hello Florent,Thank you for your answer.I’ve already tried this way also - uploading a new sample file, the problem is that all the data type definition is lost and I have to do it manually again … “Auto-detect format” is detecting nothing at all. All columns are identified as string.Best regards.Nicoleta

Have you checked your “interactiond" logs also?