manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Programmatic Operation - jobs POST
Date Tue, 20 Dec 2016 15:21:38 GMT
CONNECTORS-1361 has a patch.

Karl


On Tue, Dec 20, 2016 at 10:05 AM, Karl Wright <daddywri@gmail.com> wrote:

> Hi Cathal,
>
> First of all, notification connections do not have pipeline stages --
> they're present for the job as a whole, not for any specific sequence of
> activity within the job.  That's why "stage_id" is not meaningful for
> them.  There are only three notification stage JSON fields that are
> meaningful: stageconnectionname, stagedescription, and stagespecification.
>
> Second, it looks like "max interval" was indeed overlooked. I will create
> a ticket to add that in and will try to get it done for 2.6.
>
> Thanks,
> Karl
>
>
> On Tue, Dec 20, 2016 at 8:43 AM, Mcguinness, Cathal <
> Cathal.Mcguinness@fmr.com.invalid> wrote:
>
>> Hi Karl,
>> I am working with the programmatic operation api of MCF 2.5 and have come
>> across 2 issues:
>>
>>
>> *         There is no field for Maximum recrawl interval in the job object
>>
>> *         When I try an post a job which has an email notification stage,
>> a HTTP Status 400 - Found an unexpected node type: 'stage_id'
>>
>> Are these know issues?
>>
>>
>> Here is the notification section of the job JSON ( I have masked out the
>> email details)
>> "notificationstage": {
>>       "stage_id": "0",
>>       "stage_connectionname": "NOTIFICATION",
>>       "stage_specification": {
>>         "to": {
>>           "_value_": "",
>>           "_attribute_value": "xxx@y.com"
>>         },
>>         "from": {
>>           "_value_": "",
>>           "_attribute_value": "xxx@y.com"
>>         },
>>         "subject": {
>>           "_value_": "",
>>           "_attribute_value": "NOTIFICATION"
>>         },
>>         "body": {
>>           "_value_": "",
>>           "_attribute_value": "This is a continuous job and should not be
>> stopped outside scheduling window,"
>>         }
>>       }
>>     }
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message