So in this
edition of new from Figaf IRT
we have quite a number of new improvements that we've added here in in January and this
Is both making CPI monitoring easier,
Change tracking in CPI. We have enabled web integration so you can integrate with
Jira or whatever you are using. We have
made it possible to create test cases directly from an error, but let me show you some of these things.
So the first thing is we have a full
monitoring of all your configuration or all your development up in CPI and
that means you can go into any point in this and then see specific values across this.
Now we've added a new functionality that actually allows you to also check what happens with all your configuration
objects so you can see when a specific parameter was changed
in your landscape.
So you can see that at this stage will change these two values and that makes it a lot easier to
navigate and understand your landscape figure out what's what's happening?
Another thing that we've added into the CPI is we have monitored
Payload that that failed so you can see that if a message failed it will get our gather all of this information and
create a message that you can do something for this.
Now we've added the option for you
so you can actually create specific filters in the query so you can for instance query on a specific
Sender or receiver and with this information you're actually able to
pull out information for non
error messages and you can then get the attachments from these things.
So, one of the places where have used is is we have a flow that's uploading messages and it's getting some arrows back
but we don't want to handle all of these arrows normal way.
So, we just say this
Result was a success and then we want someone to go in and check this
Attachment and see what was going on.
And with this we actually have the option of going in and checking all of these alerts it will download them and
users can then see it.
And this connected with the next thing we have added - we have added
web hook in the support tool
for now.
So that means whenever an alert is triggered,
you can specify one or more web hooks that you wanna engage with this.
So that means you can use the web hooks either to send two to send to Solman, Jira/paperjam
or paperduty or whatever your favorite
Support to list that you want these alerts in so you can process data correctly.
So, it simply just takes all of this data It has, create a Jason payload of it and send it to
whatever system you want. You can use
CPI for this or you can use P I in your landscape.
We have created a simple integration using Jira
Zapir because it's a lot simpler to get started on. It's simple
and that's good for some reasons, but but other things it can be a little challenging with.
If you want to do more than this, we also have a full
normal API, and we're also adding web hooks to some of the other objects that we're creating on request
So, just last year
we announced this migration report that shows you what Is actually the message mappings that you're using in your
landscape. Now we have enhanced us so you can actually
see, what are the accessibility is up up and Java map means that's being used in your landscape.
So, the process is fairly simple, you log into your monitoring of your PI system,
download a report that specifies
Flows use in a specific period of time. You can then upload it to the Figaf IRT application and because we know, I
have downloaded all of your
message mapping and operation mappings, we're actually able to predict or
calculate how many times each message mappings have been executed for a period of time. So that it's really
Important when you're doing migration understanding, what's happening, what you need to test for this to to work out?
So, the reports looked like this, you've got the ICO, you got number of the message mapping and you get the number of successful
attempts that has been run, and you also got the aberration mappings here on and which are the message mapping that it's been used in.
So one thing we have are using the component based methods are learning from on your PI system to download
payloads that or messages that failed.
If you for instance have a mapping error ,you want to fix this first and then
with this new
addition, when you're creating a ticket and say this is something I want to fix,
you can actually create a test case for it also and with this test case you can run it and
validate that
we are not getting the same error again, and the message would be processed successfully.
So, this improves the the speed of development testing and validation of all
errors that you have.
So, I just want to share a little about our roadmap and it's not like it this is going to be
Probably this is the roadmap from from February,
So we're going to launch the IRT as a cloud app. So you can sign up at Figaf.com/IRT.
We're starting prices at 150 euros per month
for just the monitoring part and then it's a little higher for the
support or the the devOps package that we have,
but this makes it -
It's the same code line, same base,
but just for target at your cloud application and that makes a lot of sense since its used to monitor the IRT Cloud System.
Then, one thing that we've seen a lot of people are struggling with is the transportation
of CPI objects, and we want to
give our
view on how this can be done, and
the first thing is we want now we understand what's coming and figure it in your landscape and we want to make this
also available across your landscape so you can configure different parameters in the landscape once you're transporting it.
And then we want to enable you to do transport of a single Iflow so you can create a
transport in the IRT application assign it some values and then
Transport it to the QA and an test system. So we need to understand configure your landscape, configure configuration
for this to work. And
then we are working on documentation your
PI interfaces, so
you can see that we have this this ICO with all these information below it and
on top of it, It has some some extra information.
And the cool thing is, we can actually see that you have made for this
Iflow, you have made changes to the message mapping with this service request. You've made changes to the
communication channel with the service request so you actually know all about the history,
so instead of just having a standard document that says
his is what has what your landscape is, then we can actually show you for all purposes or what's happening across
time with a specific interface. And I think that's really important because most of the times when I see this
change version that just says
version 0.1 initial version and that's all you'd see. And now you can actually see all the the changes that has been made and the
reasons behind them.
So, I'm really looking forward to that. If you want to check it out go to Figaf.com/IRT.
If you have any other feature requests or comments or things that could be useful,
do reach out to us or me and figure out is that something we can add to make your
CPI or PI experience any better. So thanks for watching.
For more infomation >> 13abc Action News at 600AM 20190129 06000630 - Duration: 29:59. 
For more infomation >> News 2 Today's Morning Rush on January 29th - Duration: 1:09. 
For more infomation >> 13abc Action News at 630AM 20190129 06300700 - Duration: 31:59. 
For more infomation >> Promis news - Haimhausen/Bayern: Mann wird auf B13 überfahren - Kampf um sein Leben - Duration: 0:51. 
For more infomation >> Promis news - Kollaps nach Generalprobe zu „Dancing on Ice" - Duration: 2:03. 
For more infomation >> TMN News on the Go 1-29-19 - Duration: 2:04. 
For more infomation >> 歌手曲婉婷母亲或判死刑| 娛樂新聞 CBiz News - Duration: 4:06. 
For more infomation >> Eyewitness News Webcast - Duration: 2:26. 
Không có nhận xét nào:
Đăng nhận xét