How to make fields active / inactive with radio button options ?

Scenario is like this , there is layout in that layout I have nine different fields and one radio button with three diffrent options.

When I choose Option 1 then, first three fields( Field 01 , Field 02 , Field 03) should be active and last six fields (Field 04 , Field 05 , Field 06 ,Field 07 , Field 08 , Field 09) should be inactive (or locked or hidden ).

When I choose Option 2 then, first three fields( Field 01 , Field 02 , Field 03) and last three fields (Field 07 , Field 08 , Field 09) should be inactive (or locked or hidden ). and middle three fields should be active (Field 04, Field 05, Field 06 ) for data entry.

When I choose Option 3 then, first six fields( Field 01 , Field 02 , Field 03 , Field 04 , Field 05 , Field 06) should be inactive (or locked or hidden ) and last three fields should be active (Field 07, Field 08, Field 09 ) for data entry.

It is not possible to script-wise hide objects on a layout.
I suggest instead you use many layouts:

Let the radio button look like a radio, but actually be a button. Then let that button take you to various layouts:

When BUTTON 1 - you get a LAYOUT where... " first three fields( Field 01 , Field 02 , Field 03) should be active and last six fields (Field 04 , Field 05 , Field 06 ,Field 07 , Field 08 , Field 09) should be inactive (or locked or hidden )."

When click on BUTTON 2 - you get to a LAYOUT where... "When I choose Option 2 then, first three fields( Field 01 , Field 02 , Field 03) and last three fields (Field 07 , Field 08 , Field 09) should be inactive (or locked or hidden ). and middle three fields should be active (Field 04, Field 05, Field 06 ) for data entry."

To switch layouts based on buttons should be quite easy. And NO SCRIPTING...

other way, (not tested):
define for each field which option value must be true.
ex: in field1 definition: control if option=1. when option <> 1 , FM will issue an error msg if you attempt to chenge field1 value.
less smart that the previous comment, but can be done in a single layout.

Well, if you want the simple solution in ONE layout, you can use a menu-popup field, where you write out all the alternatives (they are as I understand not so many. That will take far less space and you can have it in one layout and it needs no programming.

Option1, Field 1
Option1, Field 2
Option1, Field 3
Option2, Field 1
Option2, Field 2
Option2, Field 3
Option2, Field 6
Option2, Field 7
Option2, Field 8
Option3, Field...etc.

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

true, but may become too much if the amount of conditions grow further later on??.
I think the multi-layout solution, though less smart in theory, is easier to maintain, and that should never be forgotten when you'll have to modify in a 2 years time. Also, layouts can be changed on the fly, while field definitions request you disconnect users, quite a problem in many places.

No, no no - Field definitions? You should use a value list and the contents of a value list can be based on field contents. In fact a database I was working on it was very practical to have valued lists in a related database - anyone could then define the contents of the popup. Gives new kinds of possibilities - and even better reg. maintainance!