Advanced Filtering

Right now your code is just searching for class = consent class, and patient = (patient id), you can add another search condition for consent type ="General consent for treatment" above the following line:

Set oSearchResultsP = Vault.ObjectSearchOperations.SearchForObjectsByConditions(oScsP,MFSearchFlagNone,False)

I do my search conditions a bit different but assuming your code works you can probably just add this section 

oScP.Expression.DataPropertyValuePropertyDef = ConsentTypePropId
oScP.ConditionType = MFConditionTypeEqual
oScP.TypedValue.SetValue MFDatatypeText, "General Consent for Treatment" 'replace hardcoded text with variable 
oScsP.Add -1, oScP

However, adding the above code to your search will make it return a consent object ONLY if the consent type = "General  Consent for Treatment".

Is this the desired outcome? Or did you want it to return the Consent object regardless, and take different actions if the value was not "General  Consent for Treatment".

Right now your code is just searching for class = consent class, and patient = (patient id), you can add another search condition for consent type ="General consent for treatment" above the following line:

Set oSearchResultsP = Vault.ObjectSearchOperations.SearchForObjectsByConditions(oScsP,MFSearchFlagNone,False)

I do my search conditions a bit different but assuming your code works you can probably just add this section 

oScP.Expression.DataPropertyValuePropertyDef = ConsentTypePropId
oScP.ConditionType = MFConditionTypeEqual
oScP.TypedValue.SetValue MFDatatypeText, "General Consent for Treatment" 'replace hardcoded text with variable 
oScsP.Add -1, oScP

However, adding the above code to your search will make it return a consent object ONLY if the consent type = "General  Consent for Treatment".

Is this the desired outcome? Or did you want it to return the Consent object regardless, and take different actions if the value was not "General  Consent for Treatment".

Thank you very much for sharing your knowledge :)
you are right, right now my code searches if there is anything in the class consent.

i will try your solution.

The desired outcome is: Before i make the patient status active, i need the code to check if there is a "General Consent for Treatment" consent type under consent class for the patient.

Like under the patient there are many classes, right? Consent is one of them.

now when i create a consent under that patient it will show up in that section. I just want the code to see if it is the wanted consent type or no. 
It is like searching inside a class inside another class.

In case the code didn't fine the wanted type, it will simply throw an error. 

NOTE: i am adding the code in the workflow of the patient section, not under the class or the property..

Also, i wanted to add... You are a savior :D It worked the intended way. 
Thank you very much for your time and knowledge. 

And if i may ask, how did you get this solution? I Have searched the whole internet for people explaining VBS with M-files integration. 

I have learned the basic VBS, but it is not the same as the one in M-files. M-files has these extra things like OscP, oOnePropVal, etc...

I want to understand the connection between them. But i found no courses about this or any resources. 
How can i get better in coding VBScript with M-files??

Have you seen our Developer Portal yet? It's a good starting place for all development related topics: https://developer.m-files.com/

The M-Files API reference also contains some information and example code here and there: https://www.m-files.com/api/documentation/#introduction.html

From the first look, these links looks different from what you can find on google.
Thank you very much sir :D will have a look into this as well.
Really much appreciated :)

There is a basic guide in https://www.m-files.com/user-guide/latest/eng/faq_how_do_i_write_a_visual_basic_script.html#faq_how_do_i_write_vbscript

Things like OscP, oOnePropVal etc. are just variables created in the script to temporarily hold information needed later in that same script. You can name them as you like, but it is easier to read for others if you follow naming conventions as demonstrated in the above link.

No problem, glad it worked. When I need to look something up, I usually just type M-Files API in google. The first link takes me to the API reference that Joonas provided.

Ohhhhh.. so similar to what we say int "x" or int "y"  where x, and y are the OscP and oOnePropVal.
Alrriight, that makes more sense now.
Thank s a lot sir for the clarification