ask-annie/out/857548090/transcript.txt

# Transcript: 857548090
# URL: https://vimeo.com/857548090
# Duration: 4969s (82.8 min)

[0:02] This one is a little different from the usual ask any sessions we had had earlier in the year.
[0:08] We still want you to unmute yourself and ask questions if something is unclear
[0:14] or if you have additional questions.
[0:16] And sometimes I might ask you to skip it for later in the call.
[0:21] But, for the most part, the idea of this session is to present to show you some ideas of how to use SecureTransport a little better or
[0:29] reuse it more, give you some ideas of what the server can do that you might not have realized we can do now,
[0:36] and basically talk about how to utilize your server and get better and better and get better processing for your files, get your business users happier,
[0:47] and all that funny stuff.
[0:49] And let me share my presentation.
[0:52] So I'm starting with the presentation.
[0:58] Let me know if you can see it.
[1:02] But I'll switch the live server after that. So the way this session works or what I have is five scenarios
[1:09] using some of the newer features in features in advanced routing.
[1:15] And we'll actually see them on the live server. We'll discuss how they can be used, when they can be used. I'll be happy and I'll be I hope that
[1:24] some of you will unmute yourself
[1:26] and either ask questions or mention something that they are doing that might be relevant or,
[1:31] you know, just share how you see that being useful.
[1:36] And with that being said, Hong Kong, can you just confirm that you can see my presentation at moment on the screen?
[1:44] Yes. I can see. Okay.
[1:47] Thank you. Just checking technology.
[1:49] Okay. So
[1:52] this workshop started actually as part of our summit. As you know, we had summit all over the world earlier this year.
[2:00] And here in The United States,
[2:02] we are usually doing the technical workshop for the half of the first day,
[2:08] which I usually lead for secure transport. And as part of that,
[2:12] I created that presentation and that workshop specifically for that event. However, not everyone can travel, and I didn't go to the summit outside of the North American
[2:21] continent.
[2:22] So we decided to just take the same presentation on the road. It's a little shorter. So couple of technical notes on that. You will get the presentation after the meeting, so you don't need to take screenshots if you are trying to do that. And I also have screenshots of all the screens,
[2:39] relevant screens from ST
[2:41] in the presentation itself at the bottom of it, so you'll get everything when you get the presentation.
[2:47] So
[2:49] secure transport routing,
[2:51] depending on when you joined
[2:53] actually, and when you started using secure transport, you might have seen different iteration of that. For the customers from way before 04/06, it was everything was script based. We couldn't route files around at all unless we wrote a script for it.
[3:08] Then the application framework in 04/06 going into 05/02 added the ability to do unconditional routing
[3:14] by the adding the
[3:17] allowing
[3:19] users to push files, pull files, but without any conditions
[3:23] based on file names or anything like that. Think about basic application,
[3:27] for example,
[3:28] or standard router or any of the old applications.
[3:31] Then in five three, we created the advanced routing that allowed the conditional routing finally.
[3:38] However, it still was just routing.
[3:40] The file arrives or the file doesn't arrive in the cases in the error handling, which came a little later, actually.
[3:47] So in the very first release release of advanced routing, it was a straightforward
[3:52] conditional routing,
[3:53] depending on the file name and so on. And then in five five, and now continuing that approach,
[4:01] we actually enhanced the fast routing by adding additional step, additional condition, additional places where things can be done and going into full blown orchestration
[4:11] as opposed to just conditional
[4:13] routing where you go into the routing, and then all the steps go one after another.
[4:19] In the modern world,
[4:21] yeah. In yeah. I've so in the modern world with the MFT,
[4:27] with everyone that had managed MFT for long enough had this pretty much the same problems and challenges coming one after another and basically a never ending cycle.
[4:39] Usually, there is a bunch of workarounds and all setups all over the place that had been created historically because of what was required or because of, you know, what the products could do that had never been untangled, so you might be running ten years old workarounds that are not needed anymore.
[4:55] New protocols, new channels, new ways to deliver data, data lakes, or the
[5:01] prevalence of s three lately and so on.
[5:04] There is security enhancement that they're always required.
[5:07] Anyone that works MFT knows that usual that very often security teams
[5:12] are on your head trying to get you to do things.
[5:15] There is a lot of huge amount of unconnected systems usually in the infrastructure unless you're building from scratch.
[5:23] Full visibility is very hard. And then there is the question that managed file transfer in reality should become an orchestrated file transfer. Even though we keep the old name of managed file transfer, we all know that these days,
[5:36] we have APIs in the picture.
[5:38] So we're not just file transfers even though we're still moving files, technically speaking.
[5:43] But we're also not just managing it, but fully orchestrating.
[5:46] And what we'll be talking about during this workshop is the orchestration part of it. We all know how to manage our MFQ with secure transport. It's pretty good about that. You have multiple options.
[5:58] So what we'll be talking about, okay, we got the file or there is an error condition.
[6:03] Now how to do something a little bit more intelligent based on what is happening as part of the processing,
[6:10] and not just have a straightforward list of do step one to three be done.
[6:16] In order to allow ST to become a orchestration engine,
[6:21] we had done multiple steps inside the FAST to the years. It started with the transfer side definitions.
[6:28] If you had not used STIP until three years ago, you probably don't even realize that this had been changing. But dynamic parameters all over the place that allow you to fit parameters from outside, the pluggable framework that allows the building of new protocols. That way,
[6:44] you can have s three or sample or anything you need to have.
[6:48] Number of connections control.
[6:50] Until three years ago,
[6:52] there are only the maximum per host, and everything else was tied into that. Now we have it both on the transfer side and down into the subscription level.
[7:03] The ability to do history at least for specific for some prompt calls, and this might be coming for others as well, allowing the admin to have a visibility of what actually had been coming for the list. And with the history, the ability not to pull the files over and over if your partner doesn't want to remove them. And the connection reusability,
[7:23] which is one of the newest features that allowed an s allows an SH connection to be reused for multiple files during a pull push operation if needed.
[7:33] The scheduling
[7:34] evolved
[7:35] with allowing Cronjob that probably was one one of my favorite enhancements last year.
[7:41] And now there is also the ability to do on demand pools
[7:45] from inside of an ST routing, and that what we'll be starting with the first scenario in a in a minute.
[7:52] And then in pure routing conditions
[7:55] that were usually
[7:57] so before
[7:58] late earlier this year, the conditions were only allowed to you could do a conditional route. But once into the step, it was either stop or go. There was no way to do any condition in there.
[8:10] Passing calculated values between different routes,
[8:13] allowing,
[8:15] one user to one route to calculate values and to pass them to another during a publish to account. So the publish to account can actually use variables and
[8:25] calculated values from the first one,
[8:27] and from their complete orchestration
[8:30] allowing
[8:31] a full flowchart as opposed to just the linear sending of events one after another.
[8:37] And that's all about the introduction here, and let's talk about the workshop shop scenarios.
[8:43] We'll cover five of them. That's why we have an hour and a half.
[8:47] It usually takes me about forty five to sixty minutes to talk to them if there isn't too many questions, so there should be time at the end for questions.
[8:55] However,
[8:56] we're not going to move on to the next one until we talk if you have questions or something is unclear. So pulling files only
[9:05] for based on something happening. So the first one is pulling files when another file is found.
[9:12] The common scenario is your partner creates a macro file to tell you, yep, I have all of the files, and then you go and pull all of the files now so that,
[9:22] you actually know you have all of them.
[9:24] That doesn't mean that they'll be moving together, and we'll discuss that.
[9:28] But it allows better control so that pool is not only tied to a scheduling or APIs, which is the old ways, but now you also can do it from inside of or out.
[9:40] Scenario two and three are just are working on how to get data that is received with the first connection
[9:49] or calculated on the first connection. For example, the date on the first connection
[9:54] and preserved throughout the whole routing, including sending it with the published to account out. And scenarios four and five are actually
[10:03] are the
[10:04] ability to control what happens inside of the route
[10:09] by based on what happens in every single step and creating a flowchart operation where you decide what can continue and what cannot stop. In order to achieve that, SD had a few enhancements in a row.
[10:24] As long as you are running SD five five release from February year or newer, you have all of those pieces.
[10:32] If you're running something older,
[10:34] well, go update. A lot of the staff is, well, the staff we'll be talking about is actually from earlier and from last year.
[10:42] So you might have pieces of it. What I'm sure about is that the latest pieces came in early this year or late in December
[10:50] last. So by now, considering it's August, pretty much everyone should be on the proper releases to actually be able to use that. So with that being said, let's talk about the con the first of the scenarios, which is the conditional pool.
[11:04] In the classic STF that you already used to, there are two ways to invoke the pool. One of them is by a scheduler.
[11:11] Cronjobs helped a lot there, but still a scheduler.
[11:15] Or by using the API.
[11:17] What was added is an additional step
[11:21] in advanced routing that allows you allows ST to pull
[11:32] in
[11:33] spite of a step, in the sight of an advanced routing.
[11:38] Common scenario, you go to a partner site,
[11:42] you download
[11:44] a file that says something dot ready, for example, you know, telling you that they are ready to go, and then you go and pull all the other files. So that way,
[11:53] you don't need to look for all the files every three hours,
[11:57] Or
[11:58] it it it be or as you will see, because you actually can reset both the download folder and the download pattern,
[12:07] this file that they left there,
[12:10] you they can use the name to tell you what file to look for or what the other file might be. This also can be used for something like,
[12:17] your back end application uploading a file to tell you they're ready to start processing, at which point you start going pulling from someone to start pushing to them,
[12:26] or any operation like that one.
[12:31] The basic idea is moving the ability to actually call pull from inside of a server. And with that, I'll stop sharing my presentation and move to the live server. And while I'm doing that, any questions
[12:45] so far?
[12:54] Nope.
[12:55] Okay.
[12:55] So
[12:56] browser.
[12:59] So this is the mailing list. I didn't update it on purpose because this is what I built everything based on.
[13:04] I was thinking of putting it to July 1, but it doesn't have anything that I need for this presentation. So I left it on May release. I also have a February release server that I'm using as a client or as a receiver,
[13:17] that we can look at things
[13:19] if needed. So
[13:22] our scenario
[13:24] that we're building,
[13:26] I can see a raised hand.
[13:29] You're the way, Sharia? Yep. Go ahead. Can I ask you a quick question?
[13:34] So Yeah. Is this One moment. Replacing
[13:37] replacing the business rules?
[13:39] No.
[13:42] No. It's just an additional step inside of advanced routing.
[13:47] So can it be used for business rules? Sure.
[13:51] If you think about transaction manager rules, in a way, it can be used for that. Yes.
[13:56] But it's always part of advanced routing.
[13:59] It's nothing so what they built is a special
[14:03] step called pull from partner.
[14:06] The same place where you can usually push, now you can also call pull. That's all this is all about. This is where it stands.
[14:13] So for for example, if we pull a file from the partner side
[14:17] Mhmm.
[14:18] Or if we want to push a receive a file to partner side and immediately we want to trigger an email
[14:24] notification to the
[14:26] recipient that the file has been sent.
[14:29] Or in our case,
[14:31] for example, we are pulling a file from our side, and we are sending that file to
[14:37] different users through email.
[14:40] Mhmm. We are using a business tool. Can this be done through a routing?
[14:45] When you say business tool, you mean transaction manager?
[14:49] Yes. Transaction manager. So we have Yes. You a subscription mentioned there, and we have a file name mentioned there.
[14:57] So it just trigger
[14:59] it says just send an email as an attachment to the recipient.
[15:04] Yep. You can do that out of the box. It has nothing to do with this, though. So
[15:10] remind me if I forget after I finish with this scenario, and I'll show you what you want to look at. Because we enhanced one of the transfer sites, and we have a transfer site that will do exactly what you want
[15:21] as long as for the sake basically, sending the file via mail to the customers
[15:26] the same way as if it was SSH.
[15:30] So
[15:31] okay. Cool.
[15:33] So
[15:35] okay.
[15:35] So I just don't want to close the screen I have just opened here. But as soon as I start looking in different places, I'll show you what you want to talk about.
[15:44] So
[15:45] the scenario I had built here is pretty straightforward. If a if a file
[15:50] which is called
[15:52] something dot ready
[15:54] arrives,
[15:55] go and pull from this site, which is my other server,
[16:00] by
[16:01] overwriting
[16:02] by going into the test folder
[16:05] on the remote site
[16:07] and using this pattern. Basically, go and grab all the files from the test folder.
[16:12] You can override the download folder and download pattern, and as you can see, they're yellow,
[16:18] which means you can do expressions.
[16:19] So you can actually parse the filename of the file that arrived initially to tell you what to do, or you can do anything
[16:28] with expression language as as you know and make it very, very flexible,
[16:33] overriding both the download and a pattern and
[16:38] and the folder.
[16:39] If you don't put anything here, it will grab them from the transfer site itself. If you have the transfer site properly set up,
[16:47] you don't need to do anything here.
[16:50] The local settings are telling you
[16:53] where to pull the files into ST.
[16:57] You don't need the so
[16:59] this pool will not put the files in the same sandbox where you're working with the original file.
[17:04] It doesn't need to be the same folder either.
[17:08] They can go in any folder you want in ST, and because they are pools, they basically are, like, API pools. And if this folder is a subscription folder, this will trigger whatever subscription you have on default.
[17:23] Okay. Any questions on that? So I'll show you how it works as long as I haven't broken something.
[17:30] Hello.
[17:31] Sorry. I asked a question. So for this download
[17:35] this routing Flula,
[17:37] how could we trigger this download?
[17:40] Can we trigger based on the customer download? So meaning right? So when the customer connect and then it try to download the file,
[17:49] instead of downloading from the, you know, the main box, right, we would like to trigger this advanced routing flow, you know, download from the another back end, you know, as
[17:59] No. Because
[18:01] Unfortunately,
[18:02] no. Because there is no because it's not a synchronous action.
[18:06] You can start that on the download, but the user download will still be just the file they are downloading. But
[18:14] this download can be used to trigger another download that brings the file into the server,
[18:19] and then the customer can download later the file.
[18:23] Oh, okay. So did this in that case, this routing step is something like the
[18:28] a scheduled job or frequency. Like, it cannot link with the user download. Right? That direct connection. It's correct. It's not something that is synchronous,
[18:36] but it's not tied based on time, which watches the schedule is, and it's not API based, which is coming from outside.
[18:44] It's based on something happening inside of your routing.
[18:47] It can be because of push failed, for example. If you try to push and on push failure, you know, or something like that, but it it can be a scenario I have here.
[18:58] Something produces the ready file saying we're ready to go grab the files, so we go and grab the files.
[19:04] And what I didn't explain here, and I'll show it while I'm here, this is some of the new stuff I was talking about that we enhanced. In on top of every single step, and this is not just for the new pull step, but for every step,
[19:17] the there is a condition over here for the step itself.
[19:20] And, also, you decide if you want to proceed on success or error. This will become important on the next scenarios,
[19:29] not on this one because this one is pretty straightforward.
[19:32] Because this is what will give you the orchestration,
[19:35] and because you can catch the result from the previous step,
[19:39] you can do the next step conditional on that. But I'm running a little early for that.
[19:44] One note again for the pool for partner for now,
[19:47] it only supported for the four standard protocols.
[19:50] The reason for that is pre is just technical. Those are written differently from the plug ins.
[19:55] If you require that to be working for any of the plugables
[19:59] plugable ones like ST or something, please open an idea in the ideas portal so R and D know
[20:05] which protocols are required to be done next.
[20:10] And it is David. Tim's here from, Link Group. Just a question about how does
[20:16] Secure Transport detect that file as to dot ready on the client side? Does it poll that endpoint on a on a time basis?
[20:24] You
[20:25] can do it on a time basis. Basically, this is just a route. So you need to subs to tie to a subscription.
[20:32] On the subscription, you can have a standard scheduler,
[20:35] or the user can upload the file, or you can use the API to upload the file. Mhmm. You know? It doesn't matter. In this case, I don't care. Oh, I'm caring that the file arrived and they built the subscription.
[20:47] But you also can't do it unconditionally
[20:50] on every upload when the file arrives. You can't do it if a pool fails, you know, with the conditional route. This is old stuff. That's why I'm not covering it.
[20:59] The
[21:01] point is
[21:02] that
[21:03] at the moment,
[21:04] as you know,
[21:06] before this change happened,
[21:08] you could with the file, you could go into STM, process the file, but then you couldn't read back out into the server to tell it to do something. Right? You you you could do it with an external script calling the API, but that was about it.
[21:22] So this is a easier way to do it. And that's not something that everyone will use, and I understand that. Right? We all understand that. But it's one more way to do pool, and it might be useful.
[21:35] If you have back end application that says I can't you cannot send me files between eight eight and five,
[21:41] you know, that might be a good way for them to tell you when they are ready or if they get overloaded or something.
[21:48] So
[21:50] k.
[21:52] Was there another question?
[21:54] I think I saw a hand going up.
[21:59] So, Sharia, the transfer site you want to look at is called
[22:06] yay yay. And we'll go and check on that in a second. Let me just finish what I was asked earlier about how to send the email stuff. So there is one over here that is called
[22:17] system to human.
[22:23] This checkbox, this is the new thing. You actually can send the file as a attachment,
[22:29] and you can use this transfer site pretty much the same way you're using SSH transfer sites. So if you're trying to send your files out to the your partners via email,
[22:39] use this transfer site.
[22:43] And
[22:44] there is also a variable that tells how big the files should be before you stop sending them.
[22:50] You know? Don't please don't send one gigabyte files.
[22:54] Please don't send one gigabyte files. Bump it.
[22:57] I'll see. So sorry. Can you just show me the transfer side again?
[23:02] System to human.
[23:04] System to System It's to
[23:06] already on the server. It's one of the old style ones, so it's always on your server.
[23:12] Cool. Thank you. Good to know. Yep.
[23:15] Yeah. That that so we always had that one, but it could only do attachment.
[23:20] So it only could do a link.
[23:22] What they changed
[23:23] last late last year is they now allow you to send the file itself as an attachment,
[23:28] which, you know, it's exactly your use case.
[23:31] Okay.
[23:32] And now so
[23:34] to go back to the what the question was, was how I triggered that? Well,
[23:40] I just do a pull from a site that I have the ready file on. Let's make sure I hit.
[23:47] Hold on a sec.
[23:51] No. Live presentations
[23:53] can be a little.
[24:00] So any other questions while I'm making sure that they have already filed for?
[24:13] Nope.
[24:21] And do we remember where I'm pulling from?
[24:24] Okay.
[24:27] Let's go check that.
[24:36] So I am going
[24:37] to my
[24:39] folder folder, download folder from the to the download folder.
[24:46] And then
[24:48] so here on the download folder,
[24:50] I do have already file.
[24:53] Right?
[24:55] And then it will go and drop the file from here
[24:59] and ignore the name.
[25:01] That's why I have some renames. Okay. Let's go and run that.
[25:22] Okay.
[25:25] So
[25:27] now tracking let's see if my team is up and running. It should be.
[25:32] So it found the two files because I have an unconditional looking for it.
[25:37] If we get if I did that correctly,
[25:40] nothing should happen
[25:41] for one of the files.
[25:45] Okay.
[25:46] See? That file weird file with the weird name is now coming.
[25:57] And if we go to the server lock
[26:13] Way too much server lock as usual.
[26:16] Here is where the pool files
[26:19] went through.
[26:22] And then
[26:24] it went here to find the single file
[26:27] and to graph.
[26:29] Questions on this one?
[26:38] Anything in the chat? Let me see.
[26:41] Okay. I'll come put sync links in. Okay. So any questions on this one? Anything unclear? Anything you want me to show you more before moving to the next one? Essentially, what happened here, my routing was set up. There was a single route
[26:54] over there. Two files arrived.
[26:57] This one was the one we are waiting. This one's a different one that I didn't have a route for. You can have your own route for it if you need. You know?
[27:05] Alright. We have both already.
[27:07] And then because the file was ready, it initiated another pull. And as you know,
[27:13] inbound server, that's another pull that was not scheduled, but kept on because the correct file arrived.
[27:22] Questions?
[27:29] Nope. Okay. You know what? I'll just share my whole screen for a second because
[27:35] I want to switch between the presentation
[27:38] and okay.
[27:41] Okay.
[27:43] So
[27:45] on the next one,
[27:48] as you know, you can send email notifications
[27:51] when the file arrives, or you can use the or
[27:57] or use the time or the timestamp or the the the
[28:02] time of the event to rename a file and so on. But what happens if you have long operations? For example,
[28:11] you have a PGP decryption
[28:13] and you have something else longer happening or some custom step that takes a lot of time. By the time you call timestamp, timestamp is now different. So the only way to preserve the initial timestamp or date or something else from the very beginning
[28:29] will be to save it somewhere.
[28:31] And the only place where you have where you can save things, unfortunately,
[28:36] ends up
[28:38] the file name. So you start packing it on the file name, and I know we all have played that game, but it's very annoying, especially if you need to do PGP encryption, for example,
[28:48] because PGP encryption requires the file to be with the proper name inside of the PGP archive.
[28:54] And then if you had tackled something that you want to carry, it becomes a nightmare.
[28:59] So what we created,
[29:00] what we added is a new step,
[29:03] which is pluggable. You need to download it, actually, from our support site.
[29:07] But what it allows you to save a parameter
[29:10] and use it later in the route, either to rename something
[29:16] or to put it in an email. So if you have encryption
[29:20] followed by, say,
[29:24] a push,
[29:25] you can save the time when the PGP encryption starts,
[29:29] then save the time when the PGP encryption ended. And then at the very end, when you send the mail to the end user, you can tell them when the file arrived,
[29:38] when the PGP encryption started or ended,
[29:41] and what happened after that. If you are doing pushes to three different sites,
[29:46] you can also use that to determine and to keep track of when they are scheduled. With pushes, it's easier because as we know, they go into their own event, so you can actually see them on the tracking table.
[29:57] But
[29:59] and it doesn't need to be dates. I'm working with dates here because it's easier to explain and show things than anything else.
[30:07] But that is valid also for pretty much anything you want to calculate that
[30:12] any elements that are changeable.
[30:15] For example, if you do two if you do a rename or if you are pulling a file from inside of a zip file or from inside of a PGP file, preserving the names can become a problem, especially there are multiple layers. As we all know, we have target, we have current file name, we have encrypted file name.
[30:33] But, for example, if you receive a ZIP file that was PGP encrypted,
[30:39] and then inside of the PGP encrypted, there was another ZIP or there are multiple levels of ZIP, you're going to lose some of the names of those files because we just don't have enough variables.
[30:49] What this this step allows you is to save the fire point user late.
[30:55] And back to the live server.
[30:59] Okay.
[31:22] So the scenario I'm building is pretty straightforward.
[31:30] Oops.
[31:31] Wrong one.
[31:34] In it, all I'm doing is to catch the time
[31:39] of the arrival of the file.
[31:42] And then when I send the file to the partner, I'm using that time.
[31:51] To
[31:52] put it in a special file that I sent as a trigger after the file goes out. So I send the file to the end partner, whatever arrives, and then I send them a second file which contains
[32:06] the, parameter itself, the parameter I saved.
[32:10] And, again, I'm doing that with the date
[32:12] because it's easiest to test, but it can be anything from the environment.
[32:17] And it I use a trigger file because it's easier to see. I don't need to go to the mail client and wait to see if my mail server will decide to work tonight or not, which,
[32:26] you know, test systems can be a little funny sometimes this way, especially when all the ports are closed.
[32:33] But it can be done for anything. You can send the and if you had never used the outbound trigger file, the way outbound trigger files work is that it's sent only if the push succeeds.
[32:49] So any questions here?
[32:53] Or,
[32:54] and here, what we're doing is we're setting the flow parameters on failure. I want it to stop because if I cannot set the flow parameter,
[33:02] I don't want to send the file either because it's important apparently in my scenario.
[33:07] Otherwise, it's super safe. We're not playing a lot of that. And if you look at my all of them are always running, so I always want the two steps or nothing interesting. The only thing we're doing is setting a variable.
[33:19] The five scenarios are the four scenarios I have outside of the pool. Pool itself was a little out again, but those four that we're gonna talk one after another now
[33:28] are kind of building on top of each other. So it was showing to different things that the server now can do,
[33:34] which
[33:35] are building blocks. And then the very last one will let you use every single one of them to build a full blown orchestration.
[33:43] So for this one,
[33:52] is this this one or the other one?
[33:57] This is the one.
[33:58] So,
[33:59] it's in the send date folder.
[34:02] As long as the file arrives, it get pushed out to the other server,
[34:05] and then the follow-up file is being sent. My other server, as I mentioned, is this guy over here,
[34:11] and the files will be uploaded
[34:13] over here. I already have one date, so I will just delete the old file that I was testing with during the previous run of this thing.
[34:21] And then I'll go and upload the file.
[34:26] And while I'm uploading files around, questions,
[34:29] anything you want to ask here, anything unclear,
[34:33] anything
[34:34] at all?
[34:41] It's a very silent group.
[34:52] That loss of information to consume, so we are just consuming slowly.
[34:57] I know. And I know I'm and that's why I have screenshots for all of you on the presentation.
[35:03] And I'm trying to go as slow as humanly possible,
[35:06] but, know, I have only ninety minutes, and I want to show you a lot of text today.
[35:14] Okay.
[35:15] Upload the file. It doesn't matter. It's unconditional, so let me just pick an interesting file.
[35:23] Okay.
[35:26] And
[35:27] if I didn't mess up somewhere
[35:32] oops.
[35:33] Sorry about that.
[35:36] If I don't didn't mess anywhere,
[35:38] they should show up over there. So here is my
[35:43] file, the push, the successful push, and here is the trigger file. And if I open the trigger file,
[35:53] you can see the date. And I know perfectly well it's not the correct date for you guys, but that's the date on the server.
[36:01] And if I go to the admin UI,
[36:05] oops, file tracking,
[36:09] you can see
[36:11] the nine g p g going out,
[36:14] and you also can see the timestamp that actually matches what I have in the file.
[36:19] Right?
[36:20] Of course, this time is when the server thinks the file arrived. As you can see, it's ten
[36:26] 03:18.
[36:27] That's a bit later because this is the time when the step triggered,
[36:31] right, inside of the step. But it still is earlier than when the file actually got pushed out, which is when
[36:37] the
[36:38] dates file was created to start with.
[36:42] Makes sense?
[36:43] A little bit?
[36:48] So, again, I'm doing it with the trigger file because I I do MFT. I prefer to send files around. But this variable
[36:56] and I didn't even show you how the variable is set, so oops. Sorry about that.
[37:03] Running a little bit fast here.
[37:06] The way you set the variable
[37:09] is
[37:21] is you pick whatever name you want,
[37:24] and you just put whatever expression you want. Here is my date. You can also do email. You can do a conditional here. This is and, you if you want, what, more than one, you can do the, one after another, separate lines.
[37:38] And you can specify what will happen if they're already there, which will be important The next example here, it didn't matter,
[37:45] unless you want to just do override. If you do just override and this doesn't exist, it will not get set.
[37:51] But you also can use it to override standard variables that are inside of the routing,
[37:57] almost any of them.
[38:00] Just pick up the correct name, account dot email or whatever.
[38:04] And, that way, you're using it for anything you need to. And once it is set,
[38:11] it is fully usable.
[38:13] You can use it in any of those email notifications over here, or you can use it on the next steps.
[38:20] Both for,
[38:22] what I did here was to use it inside of the trigger, but you also can use it as a condition,
[38:28] and that we'll be doing it later as well. Or you can use them for finding the transfer site name if this is what you want to do. And anywhere where we have expressions, this becomes the same way how you can use account dot name. You can now use your own variable inside of your Outlook.
[38:47] So questions on this one before I move to the next step of this exercise?
[38:57] Nope.
[38:58] So this was interesting. Right? We're sending them to someone else. But how about the very common scenario
[39:05] where
[39:06] a user called Annie uploads a file,
[39:10] the file get delivered to a second account, and the second account pushes the file or does something with the file, or the second account downloads the file. How do you notify Annie that the file got picked up? So
[39:23] let me restate that because I messed up my own email. I won't have what I'm doing.
[39:29] One user uploads the file.
[39:31] It gets delivered account to account, published to account to another account, and the other account downloads the file.
[39:38] At this point, we want to send an email to the original user that uploaded the file to tell them the file was picked up.
[39:45] How do you do that?
[39:49] Here is the problem. You are now in the second
[39:52] second subscription.
[39:54] Right? You're on the second account, so all of the email variables belong to the second account.
[39:59] So the original account email is nowhere to be seen.
[40:02] So how do you send back?
[40:05] Does this screen give you an idea? Set the variable.
[40:08] And
[40:10] when we do publish to account,
[40:13] any variable
[40:14] you set inside
[40:16] of the regional route
[40:18] will get moved
[40:20] to the routing
[40:22] to the
[40:25] routing on the second account,
[40:28] including for later purposes like downloads.
[40:32] As you know, inside of our subscriptions,
[40:35] and that that's how we actually do this trick. Inside of our subscriptions,
[40:41] we have this flow subscription attributes. If you have never used them, they are very useful and so on, but they are also hard coded inside of the subscription. So what can happen when you do publish to account,
[40:52] all of the flow subscription attributes of the original subscription are automatically
[40:57] added to the flow parameters
[41:00] on the second subscription where you published into as long as you trigger the subscription.
[41:05] Right?
[41:08] And that applies not only to the hard coded ones, but also
[41:12] to the ones that are coming
[41:14] that were added within this new step. So the scenario I will show you is exactly that.
[41:21] One user uploads a file, the file is published to another account, and the other account downloads the file. And at this point, we will see the variables from the original
[41:30] subscription
[41:32] showing up in the file. I'm not going to send the mail again. No mail server running at the moment, but you can do that back on the mail.
[41:40] One important part here, and it's very, very important, these variables,
[41:44] both the flow subscription hard coded ones and these new ones,
[41:49] are not saved in the database.
[41:51] They are saved into dot STFS folders
[41:55] inside of the subscription folders.
[41:58] So if you're cleaning your dot STFS folders,
[42:02] they'll get lost. So for example, if
[42:05] the download happens three weeks later and you had deleted your STFS folder for some reason,
[42:11] obviously, we cannot see the file.
[42:13] So
[42:14] how is that built?
[42:17] Questions on the scenario?
[42:25] My name is convention is a little weird here.
[42:29] So what I have
[42:31] is two steps.
[42:36] On the first one, I'm setting the flow parameter by setting again the current date so I can see it on the other end so we we know when the original file was uploaded here. And then the center email, which is hard coded. This can come from a variable.
[42:49] It can if you,
[42:51] if this user is authenticated for LDAP, you can grab it from the LDAP email, you know, the variable that arrived as an ldap dot, or it can come from the account or anywhere that is available,
[43:03] or you can hard code. I hard code because it's easier.
[43:07] And then
[43:08] add them at a new override.
[43:10] If the subscription where this route is called already
[43:14] have static
[43:16] variables
[43:17] with the same names, with add new override, it will override them. So whenever playing with variables, be very careful where what you're overwriting.
[43:27] Okay?
[43:28] And then I'm just published to account. And if you look at the published to account,
[43:33] I'm not doing absolutely anything interesting here besides go to the receiver account, into this folder, and trigger the subscription.
[43:41] The trigger of the subscription is mandatory because this is what will carry the flow parameters with us. If we don't trigger the subscription, we're not carrying. There is no point of doing it. So when the file arrives on the other end, we'll go and see what we do.
[43:55] Okay.
[43:56] And then on the receiver account,
[44:03] I
[44:11] have a single route.
[44:17] So
[44:18] I have two rules. One of them is with is conditional on the download. The other one is unconditional if it's not the download, which is when the when the file arrives to something. So on download,
[44:34] I have a re so if it is the client download and the trust transfer status is a success, this is nothing new. This is just the conditional route from way back when.
[44:45] We're doing a rename so I can use the variable.
[44:48] So I renamed the file with the email
[44:51] file instead to to to use the email again just to see the the value.
[44:57] And in this case, if you don't want to rename, you can just send an email or do whatever. And then I'm publishing the account back into a different into the same folder so that I can see the rename file.
[45:09] You know how it goes because I'm renaming inside of a sandbox if I want to see if any published
[45:14] it somewhere.
[45:15] So it's just a simple rename
[45:17] when the end the second user downloads the file.
[45:20] And then
[45:24] when the other the file arrives originally,
[45:29] I have another rename, which is to use the other variable.
[45:32] This is a little bit more complicated than it usually will be for anyone. I just wanted to show
[45:38] two different variables
[45:40] showing around so you can see. So here, I'm using the other one just to rename the file in a different way.
[45:45] Both of them are doing the same thing, but on different operations. One of them is when the file arrives unconditionally.
[45:51] The other one is when the file is downloaded from the end user.
[45:55] So shall we try how that goes? While I'm logging with the correct users, any questions on that?
[46:07] Nope. Okay.
[46:11] I just want to log in as my receiver and make sure I don't have files that will trip us.
[46:17] And then we'll go and
[46:20] trigger the tank.
[46:34] That's the only one I don't want here.
[46:37] The date ones
[46:39] are not a problem because it's a different date. Okay.
[46:43] So
[46:44] log out and log in as my original account.
[46:48] So what we'd expect to happen is when we go back into the receiver after this is to see the
[46:55] file named with the date.
[46:57] Right?
[47:08] File.
[47:10] Pull the file.
[47:17] As you can see, I've been doing that for a while here.
[47:20] So if
[47:24] we look at what is happening in the file tracking while we're waiting for everything to go,
[47:30] Here is the upload, the STP upload, followed by the AMI outbound. This is the publish to account.
[47:36] Right?
[47:38] This is the inbound of arriving into the receiver,
[47:43] followed by the routing
[47:45] of the file now with the date. So if I go as the receiver again,
[47:50] log out, receiver.
[48:17] And here is today's file.
[48:20] Right?
[48:22] So now I can download any of those files. So can I download all of those files? The answer is, well, maybe.
[48:29] And here is where the point is. I don't know if any of my other files you have is this dot STFS because it's a test system. So I'm going to download this file, and what I expect is after I download it for it to be renamed to the email. Right?
[48:44] So download.
[48:49] K.
[48:50] Refresh.
[48:53] And we hope it works.
[48:58] And
[49:00] here is our file.
[49:02] Got renamed because the end user downloaded, and this is the email that is hard coded all the way back when the other account uploaded the file.
[49:13] And if I can rename to it, I can use it also to send an email back to annie dot top test dot com to tell her that the file was picked up from the end user.
[49:24] Okay. Questions on this one?
[49:35] And here is the outbound user. There's the download
[49:38] followed by the routing because we went into the routing, the standard inbound outbound outbound inbound for the routing.
[49:45] Publishing back to back to the folder with it. So
[49:49] questions?
[49:52] Yeah. I have a question.
[49:54] Yeah. So
[49:56] just giving you a scenario. So for example,
[49:59] my one of my users upload a file,
[50:02] and that file goes to a
[50:05] not the user, the second user. Yes. Then the second user reprocess the file.
[50:11] And Yes. After the reprocessing,
[50:13] I have to distribute this file through an email.
[50:17] Can we achieve these things with the routing?
[50:19] Yes.
[50:21] So
[50:22] and I will show you what so that's exactly the scenario here except that I download it manually as opposed to sending to people.
[50:31] You know? So,
[50:32] in the receiver account
[50:39] come on.
[50:40] In the receiver account, remember that I had two rules. One of them, it's saying what to happen on download, but the other is what to happen when the file arrives.
[50:49] Right? So so what's the receiver you're
[50:52] referring to? Receiver and the sender? Receive I'm sorry. Receiver is my second account. The one that I pushed the file in to send the file to originally.
[51:01] So account Annie uploaded the file, and the file went to receiver, and the receiver is the one downloading
[51:08] in my side. Who is the sender in this case your case? Annie.
[51:15] Account called was
[51:17] yeah. The account called Annie.
[51:20] Oh, yeah. Yeah. Annie. Annie is uploading the file, and the receiver is the recipient of the file. Yes.
[51:28] Okay. And on and on the recipient over here, where I'm just doing the rename
[51:34] come on, open. I'm doing just the rename over here and then publishing it back.
[51:39] You can instead push the file here to anywhere it needs to go.
[51:51] So you do send,
[51:52] send to partner and select the trust site,
[51:56] which is from the type system tool
[51:59] with human.
[52:04] But you don't need to go through a second account. You can do it from the first one if you want. But if you want to do it from the second, this is where you process.
[52:13] We we do from the first account because
[52:17] Yeah. Single account is always better.
[52:19] Yeah. If you do it from the first account, you don't need to do anything special.
[52:23] You just set it up the same way you'd send the SH push.
[52:27] So
[52:28] the system to human is just a transfer site just like, any of the others.
[52:34] So if you create one, I don't have one in any of my accounts because I don't use it for anything for these examples.
[52:40] But it when you create it,
[52:43] it will show up in the list, and then they send to partner with you just to pick it up. So you just do an unconditional route, and if the file arrives,
[52:50] go and send it over there. Can you set up ever advanced routing to send to SSH?
[52:58] Sharia?
[53:01] Sorry?
[53:02] What's the question?
[53:03] Sorry. Can you ever send
[53:06] can you ever set up advanced routing to do a push to SSH?
[53:12] Yeah. We do the most of them SSH.
[53:14] Yeah. So instead of selecting on SSH side, you select the system to human side. That's that's it. Nothing else needs to happen.
[53:24] Yeah.
[53:25] I noticed that once you mentioned earlier, so that's a good good option.
[53:30] Mhmm. Okay.
[53:31] Okay.
[53:32] Any question
[53:33] on
[53:34] the whole moving of parameters around the account and sending mails back to the original sender and stuff like that that I just showed you.
[53:52] Just look at my chat
[53:54] quickly.
[53:55] Actually, I cannot.
[53:57] Okay.
[54:00] Okay. If there are no questions so that those are scenarios two and three. I never came back to three
[54:06] to to the PowerPoint for that just because it was easier to just stay on the server. But, basically, that's what we did,
[54:13] having the data from one account and one subscription move to another. What happens if this one publishes to a third one? They all come with them. Basically, they belong to it now, so they keep moving. So you can daisy chain them a lot. The common scenario when I see things like that being used is when you have one account pulling from somewhere and then distributing based on file name or based on folders
[54:37] and distributing into secondary account, then you can notify the original
[54:42] puller that the file was downloaded or pushed successfully
[54:46] or, whatever happened to it. In my case, I did it with the download because it's
[54:52] not automatic. It can happen days later and the variable is still there, which is what I wanted to show you. But you also can use it to as a mail after a successful push
[55:02] or after a successful processing in the second account or whatever you need to happen on the second account.
[55:09] Okay. Questions?
[55:13] No?
[55:15] Okay.
[55:16] So the next one,
[55:17] is a little bit more
[55:20] MFT related or, let's say, more on the managed part of the house.
[55:25] And,
[55:26] how often do you have a partner that calls you and tells you, oh, by the way, I I will be migrating to a new system, but I don't know when. So if I start stop responding, send to the second site instead instead
[55:40] of the first one.
[55:41] Or how often do you have someone calling you and telling you, have two servers, And usually, the first one is up, but if it is down, send to the second one.
[55:52] I don't know about in your world, but it happens
[55:55] occasionally.
[55:57] And
[55:58] this and it can be the second one can be on that list belong to the partner,
[56:04] or you might use it to just send back internally for prep pop up for
[56:09] processing again
[56:11] or to another group just to tell them this file couldn't be delivered. Go do something about that.
[56:16] Until now,
[56:18] we actually already had two options in STU. One of them is there is the alternate addresses on the transfer site itself. So if the protocol is the same and everything is the same, you could just put it there, but there wasn't the control of which one is we used when.
[56:35] And if something was going wrong, you never knew where it went, but it was usable for things like Doctor
[56:41] or when they call you and tell you they'll be migrating.
[56:44] Other option, of course, was to stop on error, as you know. However,
[56:50] if you stop on error, you couldn't do anything after that.
[56:55] So that if the first fails,
[56:59] the problem is that in this scenario, you want to continue on error, but stop on success. And the old routing didn't allow you that. The past routing before the last changes didn't allow you that. So the scenario we're building is
[57:12] when
[57:13] a file arrives, we try to push to one place. If we cannot, then we push to a different place instead. But we don't do the send to the fur to the second place if the first one succeeds.
[57:27] Okay. Any questions on the scenario?
[57:35] I need to go back to my on the account.
[57:53] And I call it backup server.
[57:55] It's actually alternative server or something like that. You can call, you know, the the and it doesn't even need to be both sent to partners. You can also do
[58:06] if PGP fails, do something, you know, all of that.
[58:09] The way it's built here is just to give you ideas of what you can do. Almost everywhere,
[58:15] one step can be replaced with a different kind of step. So your scenario might be if the PGP fails,
[58:22] then send
[58:23] the file to somewhere.
[58:26] And, also, they can try to process differently,
[58:28] or if you try to unzip and it's not a zip to something else and so on. So in this case,
[58:34] what
[58:35] I'm doing is
[58:39] opening.
[58:40] So first, it's a very straightforward
[58:43] send to partner, continue both on success and on the failure. Technically speaking, I don't need to proceed on success because I know I don't want to do the second send. But if I have a third step at the end
[58:54] or if I want to do email notification
[58:57] and so on,
[58:58] continue into the route makes sense. So I'm building that as if there will be more steps under the center partner,
[59:04] even though in my case, it will be easier. So the first one, nothing special here. Just send the file into the success one folder.
[59:12] But on the second one,
[59:15] I'm going into the step
[59:18] and
[59:19] oh, come on.
[59:21] I will only con this one will run only if the previous step,
[59:27] the preceding step exit status is a failure,
[59:30] which means that if the previous one succeeds, this one will never trigger, so nothing will happen. If the previous one fails,
[59:38] this one will continue. I, again, put continue on proceedings and server,
[59:42] and I'll send into the errors folder. It's on the same server because I have only one to play with, but, it's in a different folder.
[59:50] Or it can be totally different server and protocols. Don't forget. It doesn't need to go to the same place. You can be sending to one partner and then forward to an internal group. For example,
[60:01] you try to send to the external partner, and if it's failing, you send to the internal users that actually own the file.
[60:08] And this is the new thing that we added is the ability to track the previous steps.
[60:13] So that every steps, you can actually now check
[60:16] what happened in the previous step and they act based on that. In this case, I also proceed also on step on failure and success,
[60:24] which means that if I add more steps here, for example, more sent to partners or published to accounts or
[60:30] any custom steps,
[60:32] they will they will also be able to see and they'll continue. So if this one fails and this one succeeds,
[60:39] then it will be a success at this point. So the next step but because both of them continue both on success and error, the next step will always execute, and it can be conditional or not.
[60:52] Questions on that while I'm showing you how it works?
[61:01] Questions?
[61:02] Nope.
[61:03] I know it's a lot of information.
[61:06] Okay. I need to log in back. Yes. Annie.
[61:25] The way I had set it up at the moment is that my first push will fail. The second one should succeed.
[61:43] I think I didn't pick up a big file.
[61:46] Nope. It's small one. Okay.
[61:48] So let's go check what the tracking table is doing.
[61:55] So here is my first failures are happening.
[61:58] I had put it to have only
[62:00] one retry because I didn't want it to wait.
[62:05] And then here is it going out.
[62:08] And if I look at here,
[62:11] the
[62:13] remote folder on the failures is success one.
[62:16] While on success,
[62:19] it's errors as I ask you to be.
[62:24] Questions?
[62:30] Did I lose everyone?
[62:37] College is cold. No. No. No. You're we did.
[62:40] Okay.
[62:41] So that was interesting. The file went somewhere. Okay. So here is an exercise for the whole group. So
[62:49] at the end, a mail will be sent or you'll see a you know, that that the success went out. Right? The file went somewhere. If the file if the whole thing ends up in an error, you know that none of them worked. That's an easy job. Right?
[63:03] But if the
[63:04] it ends up in a success.
[63:06] So if you have a mail notifications
[63:08] on the whole package that says on success,
[63:11] notify me to tell me the file went out,
[63:14] where did the file go?
[63:17] It could go to server one or server two.
[63:24] Anyone try to guess?
[63:28] We don't know. Right? The logs.
[63:31] Well, you check the logs and then But we can get it from metadata attributes.
[63:38] Which no. There is no parameter for that,
[63:43] unfortunately.
[63:45] Or if you're sending to three different sites, how how
[63:48] do you know where it went?
[63:50] The answer is that you cannot know, unfortunately.
[63:53] Not in this case. And that's what my enhanced, the last of the scenarios you're doing, that not only sending that way, but also keeping track of what happened. How are we going to do that?
[64:03] We'll be setting variables. Remember, I told you I'll be building on top of each other.
[64:08] So the way it's built at the moment, it's going to work perfectly well, and it will be sending the files where it's supposed to go. But if you need to know where it went,
[64:17] you'll need to do some prep internally.
[64:20] Now can you check the tracking table? Yes. Can you check the server lock? If you have sentinel,
[64:25] ADI,
[64:26] embedded analytics,
[64:28] MFTOI,
[64:29] all of that will tell you where it went. Right?
[64:33] But
[64:34] what but
[64:35] how about being able to just send an email
[64:38] telling your admins that the file went
[64:41] to this server
[64:44] without the need to go and check server logs or anything like that?
[64:50] So
[64:51] how do you solve that?
[64:56] By making a little bit of a
[65:00] so,
[65:01] if you're a developer,
[65:02] and I suspect I have quite a lot of developers on on on the on the phone, how would you solve that programmatically?
[65:10] You'll set the variable you will set the flag and you'll keep or you if you're a database admin.
[65:14] How will you do that? You set the flag, and then if something succeeds, you'd raise the flag success. If something fails, you put the file on error. Right?
[65:24] So we'll do exactly that.
[65:27] So what I'm doing is I'm setting code I'm setting two flow parameters. We're just initial initiating values for them. Then I'm running the first of the pushes.
[65:37] Then I'm setting a variable,
[65:39] and I'll show you inside of the conditions.
[65:42] Then I am doing second one, then second four parameters,
[65:47] and then I'm publishing to account the file
[65:50] by renaming the file with the two variables. Again, this might be a mail or something at the end. I'm just using publish to account because it's easier for me. So at the beginning, on the set flow parameters,
[66:02] because I'm a developer, I always initialize my initial
[66:07] ize
[66:07] my variables
[66:09] because I don't want to be trying to figure out does it exist. Is it no? So I'll just create both of them with no
[66:16] or error or not going or, you know, some value that I know. That means
[66:21] I didn't send to this server.
[66:25] Right?
[66:27] Then I'm doing the push, not in case, think inside.
[66:31] Then on this flow parameter over here,
[66:35] I'm doing
[66:37] if the previous step is success and the previous step is because it was unconditional push, the previous step is the first push,
[66:44] set the main server to yes at this point. Raise the flag. I sent to the main server.
[66:50] Okay?
[66:52] So far with me?
[66:54] And don't forget here that you need to always either oops.
[66:59] Either use override or add new or override. If you do add new, nothing will happen because the variable already exists, because I already set it earlier.
[67:07] Then on the center partner, can I use the same condition as before? Can I look at the previous step again?
[67:15] I cannot because what the previous step is now the set the set parameter.
[67:20] It's not the previous push.
[67:25] So instead,
[67:26] I'm checking if the main server is still no.
[67:29] If the previous exceeded time, yes, I want to only run here if the previous is not given from, so I change what I'm doing.
[67:39] Then pretty much the same thing I did for the previous parameter, but now for the second server. So if the previous one is a success
[67:47] and the main server is a no, because that's what my scenario. If I just use the previous as a success,
[67:53] the previous of this one is
[67:56] either
[67:57] the set to partner or the previous set flow parameter.
[68:01] Because because this one is a conditional,
[68:04] if it didn't run through here,
[68:08] there is no exit.
[68:09] So
[68:11] be very careful what's preceding of what.
[68:14] Now, technically speaking, I have kept the proceeding here because both of them are conditional. They don't turn against each other.
[68:22] But I
[68:23] building your own logic sometimes can trip you, and
[68:27] that's pretty much showing to you that you have other options. You don't just need to use the preceding step. You can use a variables we already set.
[68:34] And then on publish to account,
[68:37] I'm just renaming the file to use the main server followed by the, backup server.
[68:44] And if everything is done correctly and to what what I think it should do, it will be one no. Yes.
[68:50] And, again,
[68:52] this can be used for
[68:54] putting them in email, for conditions,
[68:56] for the next processing, or whatever you need to do.
[69:01] But that's how you keep track of where we went to
[69:04] if you need to. And I'm doing it here with only two steps, but if you have a lot of steps, you can actually build your structure for each of the steps, and that will tell you perfectly well for your emails where exactly it failed.
[69:19] No.
[69:20] Any questions?
[69:25] I'll go and upload server. Alright. Server file.
[69:39] Did someone notice where I'm publishing in
[69:43] the test?
[69:48] Oops.
[69:52] Let's do that again.
[70:01] The one time I didn't check.
[70:10] It created the file. It put it over there, but because it's exactly the same file as the previous one, it didn't do anything. So let me do that clear.
[70:20] It's actually the same file. These two files were the same.
[70:25] And
[70:31] here is now the file with the
[70:34] correct timing.
[70:37] And I have something else running in the test most likely. Oh, yeah. That's one that
[70:42] so now I have the two flags up so I know where the file went.
[70:48] Can you use these variables to send them all the way to Sentinel?
[71:04] Remember that we have the mapping cover here?
[71:07] And you have to see, yes. A variable set inside of the routing can be sent to to Sentinel
[71:12] as long as you have where to house it in Sentinel. As you know, if you find that one of the nonused variables,
[71:18] you can send anything.
[71:20] It this was created in order to create to send things like the email, for example.
[71:24] But, you can also use this send this custom ones if you want to. So in this case,
[71:30] while it doesn't make much sense to do that for pushes and pulls because each of them has its own event, If you have a multistep transformation,
[71:38] for example, ZIP and PGP, as you know,
[71:41] if you go to Sentinel,
[71:43] you'll see a single event routing failed.
[71:45] Right? And you don't know if it is the ZIP or the PGP. That will allow you to send information all the way to Sentinel or ADI or whatever you're using
[71:54] or email,
[71:56] hailing,
[71:57] saying
[71:57] why the routing failed without the need to read to the log files and giving access to end users to your log files.
[72:07] So questions?
[72:19] Maria, you have your head, your hand up? You have anything, or is it from before?
[72:26] Nope. Okay.
[72:27] So
[72:29] anyone so and that's the last thing I have on my presentation, which run
[72:33] it must was my fourth time to it, and it's running a little faster every time as usually happens. So any questions or anything I showed you or anything advanced routing related?
[72:58] Any questions about ST in general? You know, if you don't have anything on the presentation, I'll take any questions at this point.
[73:15] Yeah. Hi, Annie. This is Dinesh.
[73:17] Don't have a particular question about this ST, but, like, in general, this presentation was pretty good. Actually, a lot of value add.
[73:25] I wanted to understand,
[73:27] like, this
[73:28] so many features we are in including in in ST, like, in advance routing condition for the detailed condition routing we we talked about. Subscription variable, we also talked about. So So do we have any plans to include those as part of CG or FM? Because the flows are
[73:46] being used, you know, in some of the automation that have been deployed
[73:50] by FM or CG Yeah. In case. I, yeah, I really hope no one asked me that.
[73:58] CG,
[73:58] probably not. As you know, we're retiring CG.
[74:02] We're moving into FM now, so flow manager.
[74:07] Maybe.
[74:08] So the answer is that they're not going to have full parity between ST and flow manager.
[74:14] However,
[74:15] they're willing to work with customers that require specific
[74:20] features
[74:21] to be ported up.
[74:23] So
[74:25] the answer is, if you need any of those to be in flow manager, please, please, please tell them by adding an idea.
[74:33] They need to do priorities.
[74:37] So and I know that's not the answer that we want, and that can change in a few months. As you know, that's a very
[74:45] fluid situation a little bit,
[74:48] but
[74:52] I'm hoping they'll be adding them. I just don't know what the timeline is and if they'll make all of them. But they're not going to stop creating new stuff for rescue just because it cannot catch up.
[75:02] So
[75:05] I is I'll I'll
[75:07] are all of your accounts behind phone manager?
[75:12] Yes. Dinesh? Okay. Mhmm. Yes.
[75:16] Okay. If
[75:19] something of what you saw
[75:21] is going to be useful for you, and I'm pretty sure that a lot of it looks useful.
[75:26] If you have a business case specifically, please log it into ideas.
[75:31] I'm not sure if they will ever give give up the exact,
[75:36] full blown possibility,
[75:39] but at least some of them are probably will become available sooner or later if they have enough
[75:45] need for it. At the moment, they're basically working closely based on requests.
[75:50] That's my understanding.
[75:52] And, again, it can take two to three months.
[75:55] I will remember for the next session to actually talk to r and d before the session,
[76:01] so I have a better idea of where we are. It's summer over here, everywhere. Well, not for you guys. I know for most of you, it's winter. But my part of the world, it's summer. No one is working till summer. I cannot find anyone.
[76:13] So I actually tried to catch up with r and d before the call.
[76:18] The answer is the same, you know, if you have specific case for key ideas.
[76:24] So
[76:26] So do we need to Alright.
[76:28] Write a a,
[76:29] sorry, support call for for the business cases or just liaise with the account manager?
[76:36] No. So we have an ideas portal. So if you go to community,
[76:41] and Hong Kong will post the ideas portal URL directly as well. But, on the community, there is a link to the ideas portal, which is our new way to for enhancement request.
[76:53] And that's where r and d are reading it. And you can, upvote someone else's idea, or you can add add your own idea. If you have an account executive,
[77:02] talk to them as well. If you don't, ask them where the ideas partner is. They can help you with that, or they can act on behalf.
[77:15] Thank you.
[77:16] Makes sense. And, yeah. Hong Kong, can you grab the ideas,
[77:20] portal address?
[77:23] Yep. Done. It's in the chat box.
[77:26] Okay. It just showed up. So yeah. So if you look at the chat window, it's now in the chat window. So that's the direct address, but it's also reachable to community.
[77:35] And, of course, your account executives or Hong Kong, you know, just ping him. They'll give you the address. And if you log in over there, you can see what all the ideas you had added, but you also can search ideas and you can see what other people had added
[77:48] and add your notes to someone else's idea. You know, it's an enhancement request in the in in the clear. Let's say it like that. Instead of having every customer
[77:57] thinking aside or not seeing what everyone else is asking. They just open the system for everyone. And that's not just for the flow manager people, by the way. Secure transport is also driven that way. So if you have a feature request for secure transport, for example, the on demand pool is now only for the four parameters. Right? For the four protocols,
[78:17] HTTP generic,
[78:19] FTPSSH,
[78:21] and I forgot the other one.
[78:23] If you want
[78:25] other protocols,
[78:27] please open an idea and tell them what to work on. Now are you going to get it? Not a 100% guarantee.
[78:34] But that's the enhancement request process at the moment for all of our products on the NFT suite.
[78:42] R and d of each of the product actually will evaluate.
[78:46] There's a SLA for them. We know there's a time frame for them to evaluate each of the idea.
[78:50] And then you can get your colleague or your, you friends and
[78:54] account executive with an internal x-ray to vote for it. The higher the vote, the higher the chance you will get approved.
[79:00] And then
[79:01] and and and one good thing is once you either vote or you create an idea,
[79:06] the the portal will automatically
[79:10] update you on the status. If there's any change in state, you proactively let you know, you know, what is happening to our idea, what is the status, has R and D accepted it, or if if they accepted it, is it in the road map, or is it for future consideration,
[79:23] etcetera,
[79:24] etcetera.
[79:26] Right?
[79:28] Okay.
[79:29] Thank you, Hohong. And and that again is valid for all of our products. So CFT, flow manager, all of our visibility staff,
[79:38] ST.
[79:39] This
[79:40] that's the way to talk to r and d. They listen to customers more than to us. Yep. And and sometimes you do have some
[79:48] justification
[79:49] that is confidential to your organization. Let's say, you know, revenue impact, business impact, you can actually either contact myself or you can contact your account executive
[79:58] right from X-ray, and then you can let them know we can actually help you
[80:03] ping the product manager on the background.
[80:05] Mean I Mhmm. Because they are confidential information that you you are not able to share in the public.
[80:10] Yep.
[80:14] Okay.
[80:15] So
[80:16] we are on time, surprisingly,
[80:18] this time. So last questions.
[80:21] We have a few more minutes, and that'll take pretty much anything ST related at this point or MST related.
[80:27] I don't know the lottery numbers in any country, so don't ask me for them.
[80:37] Okay. If there are no more questions, thanks everyone for joining us.
[80:42] Hong Kong will or someone will be sending you the recording and
[80:47] well, the recording will be in the link, but there the presentation as well will be included.
[80:52] And at the back of the presentation let me just show you that very quickly. Sorry.
[80:56] Just for a second.
[80:58] So at the end of my presentation
[81:01] oops.
[81:04] I have screenshots on all of these scenarios with all of the
[81:08] variables that I with all the expressions and so on so that you can actually recreate everything in your environment. And for the ones where they're most
[81:17] hard to see, I actually have them on separate screens this as well, so it just can copy paste.
[81:23] Just as a warning, if you're copy pasting, please make sure that you clear the quotes
[81:28] because this was built in Microsoft and my in the in PowerPoint,
[81:33] and Microsoft PowerPoint is changing it to the clever ones or whatever they call them.
[81:38] So, you know, but you know all of that. But, basically, I tried to put screenshots for everything
[81:45] so that,
[81:47] you actually can refer to that back when you crop the
[81:53] presentation.
[81:54] And, it will be as as a PDF, so portable and so on, but you'll have it.
[82:00] And with that, I think I don't have anything else unless someone has anything.
[82:06] And I hope that this was useful,
[82:10] and we'll talk again next quarter.
[82:12] And
[82:14] last thing, we we we'll send you a feedback survey.
[82:18] So
[82:19] please help us answer the survey.
[82:21] You know, we do read all your survey and then try to improve each time.
[82:29] If not, then thank you all for your time today. Thank you, Annie.
[82:33] Yep. Thanks, Annie.
[82:36] Thanks, everyone. Thanks, everyone. Have a wonderful day. Bye.
[82:40] Thank you. Bye bye.
[82:43] Thank you. Bye bye.