1 00:00:00,850 --> 00:00:01,490 Hi friends. 2 00:00:01,530 --> 00:00:06,860 So welcome to your training session on success factors here will be discussing about the third component 3 00:00:06,860 --> 00:00:08,440 of the UI audit. 4 00:00:08,510 --> 00:00:09,300 You are right. 5 00:00:09,410 --> 00:00:13,700 That is the query options to to take points. 6 00:00:13,700 --> 00:00:17,230 So we have the following query options 1 system query. 7 00:00:17,240 --> 00:00:22,400 Second is custom Quality and Third service operation parameters right. 8 00:00:22,550 --> 00:00:25,780 The system query system query and query string parameters. 9 00:00:25,790 --> 00:00:33,280 A plane may specify to control the amount and order of data that in order to service returns for data 10 00:00:33,280 --> 00:00:34,940 source identified by T. 11 00:00:34,980 --> 00:00:36,250 You are right. 12 00:00:36,290 --> 00:00:41,130 The names of all system query options are prefixed with the character. 13 00:00:41,240 --> 00:00:49,550 Example dollar figure dollars select etc. right to custom query provide an extension point for all data 14 00:00:49,550 --> 00:00:55,220 services specific information to be placed in the query string portion of the offer. 15 00:00:55,310 --> 00:00:56,500 You are right. 16 00:00:56,900 --> 00:01:04,190 A custom query string option is defined as any name value paired query string that we did we where the 17 00:01:04,190 --> 00:01:07,690 name of the pattern we tend to start taking with a dollar character. 18 00:01:08,300 --> 00:01:14,420 Any new Array exposed by an order the service may include one or more custom query options. 19 00:01:14,480 --> 00:01:22,330 An example from date to date has a date with the various custom query parameters that help us together 20 00:01:22,390 --> 00:01:30,890 the selected data over be activated entities service of Operation parameters. 21 00:01:30,950 --> 00:01:32,470 These represent functions. 22 00:01:32,480 --> 00:01:37,920 Example function import like Kit password policy ex post brand monitor service. 23 00:01:37,940 --> 00:01:42,680 These functions may accept 0 or more primitive type parameters. 24 00:01:43,130 --> 00:01:46,250 If a service operation request an input barometer. 25 00:01:46,310 --> 00:01:54,770 Those parameters are parsed via Q's query string name value pairs appended to the UI which identify 26 00:01:54,890 --> 00:01:57,310 the service operation that. 27 00:01:57,410 --> 00:01:58,340 Let's take an example. 28 00:01:58,340 --> 00:01:59,450 Example user I.D.. 29 00:01:59,450 --> 00:02:02,530 Group idea to track POS public static group. 30 00:02:02,540 --> 00:02:09,450 Function import for the label type but only just another value may be specified by not including the 31 00:02:09,450 --> 00:02:14,370 pattern within the query string of the UI right. 32 00:02:14,720 --> 00:02:20,020 So now we'll proceed to the system creating better test and will understand more in depth. 33 00:02:20,070 --> 00:02:29,750 Each of those same query pattern makers come into next slide so we have system query system query options 34 00:02:29,750 --> 00:02:30,800 are query string pattern. 35 00:02:30,810 --> 00:02:37,410 We just applied specified to control the amount and order of the data in order to service returns for 36 00:02:37,410 --> 00:02:43,920 the resource identified by the UI the names of all system query party records are prefixed to the dollar 37 00:02:43,920 --> 00:02:44,700 character. 38 00:02:45,390 --> 00:02:52,530 So example of this system query parameters are ordered by dollar order by dollar top and skip dollar 39 00:02:52,550 --> 00:02:55,790 figure but expand dollar format. 40 00:02:55,830 --> 00:02:58,130 Select dollar in line count. 41 00:02:58,500 --> 00:03:04,080 Now each of these query options are specified by did we should mark a sign of the source but section 42 00:03:04,080 --> 00:03:06,330 of d You are right for an example. 43 00:03:06,400 --> 00:03:09,160 Chain is so for an example. 44 00:03:09,160 --> 00:03:15,790 Here it is G.P.S. calling slash slash APAC general 4.0 effective outcome column for. 45 00:03:16,060 --> 00:03:18,200 So for this party and to service food. 46 00:03:18,210 --> 00:03:19,190 You are right. 47 00:03:19,340 --> 00:03:23,790 Then there was this part order essentially to really serve its food to are. 48 00:03:24,040 --> 00:03:26,410 Now we have the order that you want a competent do. 49 00:03:26,440 --> 00:03:30,220 We just did this whole spot Soviet specified resource as user. 50 00:03:30,220 --> 00:03:36,460 The collection is user and has pollution in this diagram if you remember and within the BTC approach. 51 00:03:36,520 --> 00:03:37,260 The key. 52 00:03:37,400 --> 00:03:42,960 So we have migrated to are not related to a specific instance of any user object. 53 00:03:43,000 --> 00:03:49,120 Now in that after we push and map we have specified all lead query options. 54 00:03:49,130 --> 00:03:53,750 So this is the front starting from question mark in the end. 55 00:03:53,810 --> 00:03:59,460 That is the query options or do you read comprehend that is the third component that you are incumbent 56 00:03:59,470 --> 00:04:03,110 against currently working upon. 57 00:04:03,390 --> 00:04:10,640 So as mentioned each of these query options are specified after the question of the question mark itself. 58 00:04:10,840 --> 00:04:22,250 The on the query options starts right the question markets the significance or the identifier that signifies 59 00:04:22,250 --> 00:04:29,880 the start of the query options barometers all the options should be separated by ambushing and also 60 00:04:29,880 --> 00:04:33,110 they should not be any space between the percent and dollar. 61 00:04:33,720 --> 00:04:36,580 But there can be space before 10 percent. 62 00:04:38,340 --> 00:04:46,080 Think of like this example as GDP has grown substantially in system afford to accept this outcome colorful 63 00:04:46,160 --> 00:04:52,870 filthy which is a port and in order to do so this is the first comparable to the EU brand and the second 64 00:04:53,260 --> 00:04:56,030 component is that this was far to design that collection. 65 00:04:56,020 --> 00:05:02,920 We have not moved moving to predict a specific instance of these objects or the entire collection and 66 00:05:02,920 --> 00:05:03,960 yet operating upon. 67 00:05:04,390 --> 00:05:12,580 And then they push and Mark and then we have data format difficulty Jason and then separated by 10 percent 68 00:05:12,790 --> 00:05:14,790 we a. second ready bedroom. 69 00:05:14,830 --> 00:05:22,670 Second creating option to select so we had first but a format then started select and then we have specified 70 00:05:22,680 --> 00:05:31,970 D columns and they put defeated stepped down there in the user object to predict and then we in IT specifying 71 00:05:32,050 --> 00:05:38,150 that a percent dollar topic equal to 10 and then in a percent and then we have the writing this space 72 00:05:38,150 --> 00:05:44,040 over here puts indeed and percent and a dollar where the dollar for that is equal to the five 20 plus 73 00:05:44,120 --> 00:05:46,910 any surveys and there is no defined for being specified. 74 00:05:46,910 --> 00:05:52,170 So we want to find out how those users make. 75 00:05:52,390 --> 00:05:57,180 So what we are saying is there should not be any space between and an end percentile. 76 00:05:57,360 --> 00:06:00,850 Here we are in space between 8 and 10 percent right. 77 00:06:01,210 --> 00:06:03,910 So we are saying that they start being a space. 78 00:06:04,000 --> 00:06:05,080 Does the replication upward. 79 00:06:05,080 --> 00:06:10,910 So let's say there is tries to discredit festival let's go to the northwest but think of this. 80 00:06:11,310 --> 00:06:17,170 And it's going to be postponed to the next day of try to do good discretely from here. 81 00:06:17,200 --> 00:06:23,320 Now we're providing the authorizations and then if we try to execute this query let's see what comes 82 00:06:23,320 --> 00:06:23,460 up. 83 00:06:25,660 --> 00:06:27,310 So we get the results. 84 00:06:27,820 --> 00:06:33,520 And here we are seeing the department value also being provided to them a deeper level 70 Energy Department 85 00:06:33,520 --> 00:06:35,050 values are being provided. 86 00:06:35,250 --> 00:06:40,180 So that since the food is not getting applied because of the reason that there is a space between it 87 00:06:40,180 --> 00:06:43,270 and push into dollar so physical space. 88 00:06:43,270 --> 00:06:45,360 Yes physical space. 89 00:06:45,460 --> 00:06:53,960 Now like this and then now move just space now to execute it again and then when this man speaks good 90 00:06:53,970 --> 00:06:58,190 is defeated by all departments are coming with not the same values. 91 00:06:58,200 --> 00:07:03,660 Looking out for the heads for the food that is being placed is an important point and between the ampersand 92 00:07:03,770 --> 00:07:10,820 and a dollar or any other creative barometer query option parameter should not be in space. 93 00:07:10,930 --> 00:07:15,860 If there is a space offered an impression then that denotes the end of the query option but it does 94 00:07:16,030 --> 00:07:18,120 no particularly option value does. 95 00:07:18,220 --> 00:07:19,460 I'd be entertained. 96 00:07:19,570 --> 00:07:25,450 So there's an important point need to take into consideration while writing the queries since in the 97 00:07:25,450 --> 00:07:30,460 above way the space between the important end of the filter and the dollar for the clock floods will 98 00:07:30,460 --> 00:07:36,190 not be honored and output to reproduce without G for being applied and that is working. 99 00:07:36,520 --> 00:07:37,280 So just. 100 00:07:40,410 --> 00:07:48,440 The point to note over here is that OK once the even if we have any space between if dead space before 101 00:07:48,450 --> 00:07:50,870 the temperature inside then it might execute. 102 00:07:50,880 --> 00:07:57,240 So we have 10 percent of it yet deployed in space a little more than one space over here and then we 103 00:07:57,240 --> 00:07:59,010 try to execute this query. 104 00:07:59,100 --> 00:08:02,170 We still get the jitters have the new department as. 105 00:08:02,680 --> 00:08:05,190 So that is particularly taken care of. 106 00:08:05,190 --> 00:08:12,070 And that is more disturbed by the poor data really injured so low that I should not pose any problem. 107 00:08:12,380 --> 00:08:18,340 But the important point is between the specified the question and then we specify the credit perimeter 108 00:08:18,710 --> 00:08:24,750 within space then that particular date is not honored and that's is you can see that these values of 109 00:08:24,750 --> 00:08:32,190 the department are being written where the department is given not equal to be a penny as well right. 110 00:08:32,210 --> 00:08:34,920 And we we wanted to shore up the department. 111 00:08:35,130 --> 00:08:36,510 And so that is it. 112 00:08:36,530 --> 00:08:43,940 We have to remove this the space can put in another and executing correctly it values so French in the 113 00:08:43,940 --> 00:08:49,880 upcoming session we'll be looking into each of these system query pattern with test in Quest details 114 00:08:50,440 --> 00:08:55,250 and will be understanding the various particularities the Vegas format in which these values can be 115 00:08:55,250 --> 00:09:03,240 provided to it and other nuances on executing all of these system creating pattern because one by one 116 00:09:04,570 --> 00:09:06,220 the Flints Dylan stages. 117 00:09:06,730 --> 00:09:08,440 And if you have any happier. 118 00:09:09,070 --> 00:09:09,360 Thank you.