What are characteristics of UI integration cards? (Choose two.)
35 comments · newest first
JO
Johana
11 months ago
Is the HTMLS.ForwardAuth Token really necessary? Sounds odd.
PH
Phil
12 months ago
Don't forget about the subaccount level for destinations!
ER
Eric
12 months ago
Wait, they can only consume from SAP? That seems limiting.
AR
Arthur
1 year ago
Totally agree, that's a key feature!
AR
Arlette
1 year ago
They can call multiple backend systems.
ST
Stefan
1 year ago
I vaguely recall something about the HTMLS.ForwardAuth Token, but I can't remember if it was a requirement for all destinations or just specific ones.
RA
Raul
1 year ago
I practiced a question similar to this, and I remember that UI integration cards can only pull data from specific sources, which makes me think option C could be misleading.
RE
Rene
1 year ago
I'm not entirely sure, but I feel like option D might be correct since destinations usually need to be set up at the subaccount level.
PI
Pilar
1 year ago
I think option B sounds familiar because I remember something about UI integration cards being able to interact with multiple systems.
SH
Shantay
1 year ago
I'm a bit confused by this question. I'm not sure what the HTMLS.ForwardAuth Token property is, and I don't think UI integration cards are limited to just SAP systems. I'll have to think this through a bit more.
AR
Arlette
1 year ago
Okay, I've got this. UI integration cards can call multiple backend systems, that's definitely one. And they don't have to be limited to just SAP systems, so I'll go with that as the other characteristic.
EL
Elfriede
1 year ago
Hmm, this is a tricky one. I'm not sure about the HTMLS.ForwardAuth Token property, but I know UI integration cards can call multiple backend systems, so that's one I'm confident about.
SE
Selma
1 year ago
I'm not too familiar with UI integration cards, but I think the key is to focus on the characteristics that are mentioned in the question. I'll try to eliminate the options that don't seem to fit.
BU
Buffy
1 year ago
UI integration cards are like the Swiss Army knives of the UI world - they can do it all! Except for consuming data from SAP systems, apparently. That's like asking a chef to only use ingredients from one grocery store.
MI
Mirta
1 year ago
B) They can call multiple backend systems.
AR
Arthur
1 year ago
A) Destinations must have the HTMLS.ForwardAuth Token property set to true.
MA
Mariann
2 years ago
I'm going with B and D. Connecting to multiple systems is super useful, and maintaining the destinations at the subaccount level makes a lot of sense. As for the HTMLS.ForwardAuth Token, that's just tech talk for 'magic sauce'.
LA
Lauran
1 year ago
I agree, being able to connect to multiple systems is definitely a key feature. And keeping the destinations at the subaccount level just makes everything more organized.
KA
Kati
1 year ago
D) Destinations must be maintained at the SAP BTP subaccount level.
ST
Stephania
2 years ago
B) They can call multiple backend systems.
PE
Pete
2 years ago
A and B sound right to me. The HTMLS.ForwardAuth Token is crucial, and being able to call multiple backends is a key feature of UI integration cards.
EL
Elroy
1 year ago
A and B sound right to me. The HTMLS.ForwardAuth Token is crucial, and being able to call multiple backends is a key feature of UI integration cards.
VE
Verlene
1 year ago
B) They can call multiple backend systems.
MO
Mollie
2 years ago
A) Destinations must have the HTMLS.ForwardAuth Token property set to true.
CR
Cristina
2 years ago
Hmm, I'm not sure about C. I thought UI integration cards could consume data from any system, not just SAP. And the HTMLS.ForwardAuth Token is definitely important for authentication.
MA
Maile
1 year ago
B) They can call multiple backend systems.
NA
Nathan
2 years ago
A) Destinations must have the HTMLS.ForwardAuth Token property set to true.
KE
Kenia
2 years ago
I'm pretty sure B and D are the correct answers. UI integration cards can connect to multiple backend systems, and the destinations need to be maintained at the subaccount level.
DA
Dana
1 year ago
That makes sense, thanks for clarifying!
KA
Kathrine
1 year ago
So, the correct answers are B and D for characteristics of UI integration cards.
DE
Delsie
1 year ago
I agree, D is also correct because destinations must be maintained at the SAP BTP subaccount level.
RI
Rickie
2 years ago
I think B is correct because UI integration cards can call multiple backend systems.
ST
Stephaine
2 years ago
That makes sense. It's important to have the correct setup for UI integration cards to work properly.
LA
Laquanda
2 years ago
I agree with you, Laquanda. I also believe that destinations must be maintained at the SAP BTP subaccount level.
ST
Stephaine
2 years ago
I think the characteristics of UI integration cards include calling multiple backend systems.