• 0 Vote(s) - 0 Average
  • 5
  • 4
  • 3
  • 2
  • 1
Thread Modes

REST - Group email & unknown error
#1
Hello
We follow our integration with EV and orchestration tool...
I've 2 issues when using POST  REQUESTS/XXXX/TASKS

1. Must provide acting group info with email  (group_mail" : "xxxx@xxxx.com",) BUT what if group has no email address?? We've a lot of groups without email address.. Notifications to group are sent to member's address....

2. When I post one task creation request to one ticket, I got an unknown error message, not documented at wiki and don't know the reason. We're posting



POST https://OUR_SERVER/api/v1/50004/requests/I017815/tasks

with body
{
  "action_type_id": "17",
  "group_mail" : "someaddres@domain.com",
  "Elapsed_Time": "20",
  "description": "Some description for action"
}

and got error 405 Method not allowed with following text
{ "error": "Invalid catalog identifier"}

I017815 is a valid ticket, has nothing special and, 17 is one valid action type (proceesing or "action related with ticket")..... as I see, we're using right sintax

any help with this?

thanks a lot

#2
(06-20-2017, 07:46 AM)egomez Wrote: Hello
We follow our integration with EV and orchestration tool...
I've 2 issues when using POST  REQUESTS/XXXX/TASKS

1. Must provide acting group info with email  (group_mail" : "xxxx@xxxx.com",) BUT what if group has no email address?? We've a lot of groups without email address.. Notifications to group are sent to member's address....

2. When I post one task creation request to one ticket, I got an unknown error message, not documented at wiki and don't know the reason. We're posting



POST https://OUR_SERVER/api/v1/50004/requests/I017815/tasks

with body
{
  "action_type_id": "17",
  "group_mail" : "someaddres@domain.com",
  "Elapsed_Time": "20",
  "description": "Some description for action"
}

and got error 405 Method not allowed with following text
{ "error": "Invalid catalog identifier"}

I017815 is a valid ticket, has nothing special and, 17 is one valid action type (proceesing or "action related with ticket")..... as I see, we're using right sintax

any help with this?

thanks a lot

I think that action_type_id=17 is forbidden, you must use "tasks" that not a workflow's brick :
(((AM_ACTION_TYPE.IMPACT_DELAY = 0)) OR (AM_ACTION_TYPE.IMPACT_DELAY is null)) AND (((AM_ACTION_TYPE.IS_WORKFLOW = 0)) OR (AM_ACTION_TYPE.IS_WORKFLOW is null))

Could you try with action_type_id=19?

P.ABBE
ABBE Philippe, proud to be a member of EV CONNECT FORUM since Nov 2015.

#3
Hello Philippe
I've tryed with action_types 10, 11, 12, 19. .all action_types included within your filter (as I undestand, must be action_type not usable into workflow?)
Same result.
After some test, we've seen that can not insert via API one action with impact delay, so..
There is any way to insert some action that must be sent to one group for resolving? (as i understand, this kind of task must impact on delay, but...)
At this point i've set as 0 impact_delay field for action_type_id 17 (for testing) but can not use it at production enviroment (if i set impact_delay=0 then, these actions will not affect SLAs, isn't it?)

Do you can say something about groups with no email address??

thanks a lot

#4
Hello
Something has been changed at wiki???
https://wiki.easyvista.com/xwiki/bin/vie...%2Drequest

A few days ago there was another info at this page... as I remember
there were some optional parameters (now it's empty)
there was info about group identification.. now only group_email, I remember something about identify by group_xx using group name (xx = REST user language) and now there is no info...

perhpas, question is how stable is the API? somethings it seems to be a beta Sad

bye

#5
(06-21-2017, 02:39 AM)egomez Wrote: Hello Philippe
I've tryed with action_types 10, 11, 12, 19. .all action_types included within your filter (as I undestand, must be action_type not usable into workflow?)
Same result.
After some test, we've seen that can not insert via API one action with impact delay, so..
There is any way to insert some action that must be sent to one group for resolving? (as i understand, this kind of task must impact on delay, but...)
At this point i've set as 0 impact_delay field for action_type_id 17 (for testing) but can not use it at production enviroment (if i set impact_delay=0 then, these actions will not affect SLAs, isn't it?)

Do you can say something about groups with no email address??

thanks a lot

Hello,
Sorry i've not experience (for the time being) in REST, only use SOAP and i'm pretty sur that "POST  /requests/{rfc_number}/tasks" can only store an action that is gone. 
I'think that EZV_CreateRelatedAction don't exist (for the moment) in REST.
For your problem, perhaps you could create a task in REST and trigger it for creating RelatedAction in SOAP (in Business rules).

As you say, REST still in developpment but respond to small needs.

P.ABBE
ABBE Philippe, proud to be a member of EV CONNECT FORUM since Nov 2015.

#6
(06-23-2017, 07:44 AM)ABBE Philippe Wrote:
(06-21-2017, 02:39 AM)egomez Wrote: Hello Philippe
I've tryed with action_types 10, 11, 12, 19. .all action_types included within your filter (as I undestand, must be action_type not usable into workflow?)
Same result.
After some test, we've seen that can not insert via API one action with impact delay, so..
There is any way to insert some action that must be sent to one group for resolving? (as i understand, this kind of task must impact on delay, but...)
At this point i've set as 0 impact_delay field for action_type_id 17 (for testing) but can not use it at production enviroment (if i set impact_delay=0 then, these actions will not affect SLAs, isn't it?)

Do you can say something about groups with no email address??

thanks a lot

Hello,
Sorry i've not experience (for the time being) in REST, only use SOAP and i'm pretty sur that "POST  /requests/{rfc_number}/tasks" can only store an action that is gone. 
I'think that EZV_CreateRelatedAction don't exist (for the moment) in REST.
For your problem, perhaps you could create a task in REST and trigger it for creating RelatedAction in SOAP (in Business rules).

As you say, REST still in developpment but respond to small needs.

P.ABBE


(06-23-2017, 07:44 AM)ABBE Philippe Wrote:
(06-21-2017, 02:39 AM)egomez Wrote: Hello Philippe
I've tryed with action_types 10, 11, 12, 19. .all action_types included within your filter (as I undestand, must be action_type not usable into workflow?)
Same result.
After some test, we've seen that can not insert via API one action with impact delay, so..
There is any way to insert some action that must be sent to one group for resolving? (as i understand, this kind of task must impact on delay, but...)
At this point i've set as 0 impact_delay field for action_type_id 17 (for testing) but can not use it at production enviroment (if i set impact_delay=0 then, these actions will not affect SLAs, isn't it?)

Do you can say something about groups with no email address??

thanks a lot

Hello,
Sorry i've not experience (for the time being) in REST, only use SOAP and i'm pretty sur that "POST  /requests/{rfc_number}/tasks" can only store an action that is gone. 
I'think that EZV_CreateRelatedAction don't exist (for the moment) in REST.
For your problem, perhaps you could create a task in REST and trigger it for creating RelatedAction in SOAP (in Business rules).

As you say, REST still in developpment but respond to small needs.

P.ABBE

Hi,

We already get the same problem for a client, and the solution was using 2 custom fields to store : 
- action_type_id
- group_id

and then, a BR uses a sql query to create theses actions.

You're right while saying you can't create actions with WebServices, it's only tasks, so closed at creation time.

Hope to be helpfull Wink
CLEONARD, proud to be a member of EV CONNECT FORUM since Feb 2017.






Users browsing this thread: 1 Guest(s)