Class ProfileSelection
Round-up is surfaced, never silent
When a requirement has no exact service-profile tier the wizard selects the smallest tier that
satisfies it (3000 → 5000) rather than erroring - but rounding up increases the billed
bandwidth, so it is recorded here (isRoundedUp(), roundedUpByMbps()) and rendered
in the plan. A non-interactive caller still gets a valid plan (the smallest covering tier); an
interactive caller can confirm the increase before provisioning.
Choice is exposed, with a valid default
getAlternatives() lists every covering candidate, the wizard's default first. When more
than one candidate can carry the bandwidth (hasChoice()), the MCP layer may elicit a choice;
either way getSelectedProfileUuid() / getSelectedSellerRegion() are the default the
plan is built with, so the plan is always executable without interaction.
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionbooleanWhether there is more than one covering candidate - a genuine decision point an interactive layer (the MCP server) can elicit, rather than a forced single choice.intHow many Mbps the billed bandwidth was rounded up by, or0when no round-up occurred.
-
Constructor Details
-
ProfileSelection
public ProfileSelection()
-
-
Method Details
-
hasChoice
public boolean hasChoice()Whether there is more than one covering candidate - a genuine decision point an interactive layer (the MCP server) can elicit, rather than a forced single choice.- Returns:
truewhen at least two profiles cover the requested bandwidth
-
roundedUpByMbps
public int roundedUpByMbps()How many Mbps the billed bandwidth was rounded up by, or0when no round-up occurred.- Returns:
selectedTierMbps - requestedMbps, floored at 0
-